View PM7380_4043899.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sie rra,inc., and for its customers? internal use PM7380 freedm?-32p672 frame engine and datalink manager 32p672 data sheet proprietary and confidential issue 5: august 2001
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use i public revision history issue no. issue date details of change issue 1 february, 18, 1999 created document. issue 2 may 30, 1999 added pinout. issue 3 jan, 2000 minor corrections. issue 4 july 2000 minor corrections to some dc and ac timing parameters issue 5 august 2001 added patent information to legal footer.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use ii contents 1 features...............................................................................................1 2 applications........................................................................................4 3 references .........................................................................................5 4 application examples ......................................................................6 5 block diagram....................................................................................8 6 description .........................................................................................9 7 pin diagram ........................................................................................12 8 pin description ................................................................................13 9 functional description ...............................................................38 9.1 high speed multi-vendor integration protocol (h-mvip) ......................................................................................38 9.2 high-level data link control (hdlc) protocol.........38 9.3 receive channel assigner ................................................39 9.3.1 line interface translator (lit) ........................41 9.3.2 line interface..........................................................42 9.3.3 priority encoder ...................................................42 9.3.4 channel assigner ..................................................42 9.3.5 loopback controller .........................................43 9.4 receive hdlc processor / partial packet buffer...43 9.4.1 hdlc processor .....................................................44 9.4.2 partial packet buffer processor ..................44 9.5 receive dma controller ...................................................46 9.5.1 data structures ....................................................46
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use iii 9.5.2 dma transaction controller...........................56 9.5.3 write data pipeline/mux .......................................56 9.5.4 descriptor information cache ........................56 9.5.5 free queue cache ..................................................57 9.6 pci controller......................................................................57 9.6.1 master machine ......................................................58 9.6.2 master local bus interface..............................60 9.6.3 target machine .......................................................61 9.6.4 cbi bus interface ...................................................63 9.6.5 error / bus control .............................................63 9.7 transmit dma controller.................................................63 9.7.1 data structures ....................................................64 9.7.2 task priorities ........................................................76 9.7.3 dma transaction controller...........................76 9.7.4 read data pipeline..................................................76 9.7.5 descriptor information cache ........................76 9.7.6 free queue cache ..................................................77 9.8 transmit hdlc controller / partial packet buffer77 9.8.1 transmit hdlc processor..................................77 9.8.2 transmit partial packet buffer processor78 9.9 transmit channel assigner .............................................80 9.9.1 line interface translator (lit) ........................82 9.9.2 line interface..........................................................82 9.9.3 priority encoder ...................................................83
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use iv 9.9.4 channel assigner ..................................................83 9.10 performance monitor .......................................................84 9.11 jtag test access port interface...................................84 9.12 pci host interface ...............................................................84 10 normal mode register description ........................................89 10.1 pci host accessible registers .......................................89 11 pci configuration register description ............................252 11.1 pci configuration registers.........................................252 12 test features description .......................................................263 12.1 test mode registers ........................................................263 12.2 jtag test port .....................................................................264 12.2.1 identification register .....................................265 12.2.2 boundary scan register ..................................265 13 operations ......................................................................................282 13.1 toctl connections ............................................................282 13.2 jtag support........................................................................282 14 functional timing .........................................................................289 14.1 receive h-mvip link timing ...............................................289 14.2 transmit h-mvip link timing.............................................290 14.3 receive non h-mvip link timing ......................................291 14.4 transmit non h-mvip link timing ....................................293 14.5 pci interface ........................................................................294 14.6 bert interface ....................................................................303 15 absolute maximum ratings........................................................305
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use v 16 d.c. charact eristics....................................................................306 17 freedm-32p672 timing characteristics.................................308 18 ordering and ther mal information ......................................318 19 mechanical information.............................................................319
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use vi list of figures figure 1 ? h-mvip protocol ....................................................................38 figure 2 ? hdlc frame...............................................................................39 figure 3 ? crc generator.......................................................................39 figure 4 ? partial pa cket buffer structure ..................................45 figure 5 ? receive packet descriptor...............................................47 figure 6 ? receive packet descriptor table...................................50 figure 7 ? rpdrf and rpdrr qu eues ...................................................52 figure 8 ? rpdrr queue operation......................................................54 figure 9 ? receive channel des criptor reference table.........55 figure 10 ? gpic address map ................................................................62 figure 11 ? transmit descriptor..........................................................64 figure 12 ? transmit descriptor table .............................................68 figure 13 ? tdrr a nd tdrf qu eues .......................................................70 figure 14 ? transmit channel descriptor reference table ....72 figure 15 ? td linking................................................................................75 figure 16 ? partial pa cket buffer structure ................................79 figure 17 ? input observation cell (in_cell) .................................279 figure 18 ? output cell (out_cell) ...................................................280 figure 19 ? bi-directional cell (io_cell) .........................................280 figure 20 ? layout of output enable and bi-directional cells ..............................................................................................................281 figure 21 ? boundary sc an archite cture ......................................283 figure 22 ? tap controller finite state machine ........................285
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use vii figure 23 ? receive 8.192 mbps h-mvip link timing .........................289 figure 24 ? receive 2.048 mbps h-mvip link timing .........................290 figure 25 ? transmit 8.192 mbps h-mvip link timing.......................290 figure 26 ? transmit 2.048 mbps h-mvip link timing.......................291 figure 27 ? unchannelised receive link timing ............................292 figure 28 ? channelised t1/j1 receive link timing .......................292 figure 29 ? channelised e1 receive link timing ............................293 figure 30 ? unchannelised transmit link timing..........................293 figure 31 ? channelised t1/j1 transmit link timing .....................294 figure 32 ? channelised e1 transmit link timing .........................294 figure 33 ? pci read cycle ....................................................................296 figure 34 ? pci write cycle ..................................................................297 figure 35 ? pci target disconnect ....................................................298 figure 36 ? pci target abort................................................................299 figure 37 ? pci bus request cycle ....................................................299 figure 38 ? pci initiator abort termination ...................................300 figure 39 ? pci exclusive lock cycle ...............................................301 figure 40 ? pci fast back to back.......................................................303 figure 41 ? receive bert port timing ...............................................303 figure 42 ? transmit bert port timing .............................................304 figure 43 ? receive data & frame pulse timing (2.048 mbps h-mvip mode) ..................................................................................................310 figure 44 ? receive data & frame pulse timing (8.192 mbps h-mvip mode) ..................................................................................................310 figure 45 ? receive data timing (non h-mvip mode) ...................... 311
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use viii figure 46 ? bert input timing ............................................................... 311 figure 47 ? transmit data & frame pulse timing (2.048 mbps h-mvip mode).....................................................................................313 figure 48 ? transmit data & frame pulse timing (8.192 mbps h-mvip mode).....................................................................................314 figure 49 ? transmit data timing (non h-mvip mode) ....................314 figure 50 ? bert output timing ...........................................................315 figure 51 ? pci interface timing .........................................................316 figure 52 ? jtag port interface timing............................................317 figure 53 ? 329 pin plastic ball grid array (pbga) .......................319
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use ix list of tables table 1 ? line side interface signals (154) ........................................13 table 2 ? pci host interface signals (52) ..........................................23 table 3 ? miscellaneous in terface signals (58).............................32 table 4 ? production test interface signals (0 - multiplexed)33 table 5 ? power and ground signals (65) .........................................35 table 6 ? receive packet descriptor fields....................................47 table 7 ? rpdrr queue element ............................................................53 table 8 ? receive channel descriptor reference table fields ................................................................................................................55 table 9 ? transmit descriptor fields ................................................65 table 10 ? transmit descriptor reference.....................................71 table 11 ? transmit channel descriptor reference table fields ...................................................................................................73 table 12 ? normal mode pci host accessible register memory map ........................................................................................................84 table 13 ? pci configuration register memory map.....................88 table 14 ? big endian format................................................................ 119 table 15 ? little endian format .......................................................... 119 table 16 - receive links #0 to #2 configuration ...........................130 table 17 - receive links #3 to #31 configuration .........................132 table 18 ? crc[1:0] settings...................................................................139 table 19 ? rpq_rdyn[2:0] settings ......................................................150 table 20 ? rpq_lfn[1:0] settings..........................................................151 table 21 ? rpq_sfn[1:0] settings .........................................................151
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use x table 22 ? tdq_rdyn[2:0] settings.......................................................185 table 23 ? tdq_frn[1:0] settings .........................................................185 table 24 ? crc[1:0] settings...................................................................213 table 25 ? flag[2:0] settings .................................................................219 table 26 ? level[3:0]/trans settings ..................................................221 table 27 - transmit links #0 to #2 configuration .........................239 table 28 - transmit links #3 to #31 configuration .......................241 table 29 ? test mode register memory map ..................................264 table 30 ? instruction register ........................................................265 table 31 ? boundary scan chain .........................................................265 table 32 ? freedm?toctl connections ............................................282 table 33 ? freedm-32p672 absolute maximum ratings.................305 table 34 ? freedm-32p672 d.c. characteristics.............................306 table 35 ? freedm-32p672 link input (figure 43 to figure 46)....308 table 36 ? freedm-32p672 link output (figure 47 to figure 50) 311 table 37 ? pci interface (figure 51) ...................................................315 table 38 ? jtag port interface (figure 52)......................................316 table 39 ? freedm-32p672 ordering information..........................318 table 40 ? freedm-32p672 thermal information ............................318
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 1 1 features single-chip multi-channel hdlc controller with a 66 mhz, 32 bit peripheral component interconnect (pci) revision 2.1 bus for configuration, monitoring and transfer of packet data, with an on-chip dma controller with scatter/ gather capabilities. supports up to 672 bi-directional hdlc channels assigned to a maximum of 32 h-mvip digital telephony buses at 2.048 mbps per link. the links are grouped into 4 logical groups of 8 links. a common clock and a type 0 frame pulse is shared among links in each logical group. the number of time-slots assigned to an hdlc channel is programmable from 1 to 32. supports up to 672 bi-directional hdlc channels assigned to a maximum of 8 h-mvip digital telephony buses at 8.192 mbps per link. the links share a common clock and a type 0 frame pulse. the number of time-slots assigned to an hdlc channel is programmable from 1 to 128. supports up to 672 bi-directional hdlc channels assigned to a maximum of 32 channelised t1/j1 or e1 links. the number of time-slots assigned to an hdlc channel is programmable from 1 to 24 (for t1/j1) and from 1 to 31 (for e1). supports up to 32 bi-directional hdlc channels each assigned to an unchannelised arbitrary rate link, subject to a maximum aggregate link clock rate of 64 mhz in each direction. channels assigned to links 0 to 2 support a clock rate of up to 51.84 mhz. channels assigned to links 3 to 31 support a clock rate of up to 10 mhz. supports three bi-directional hdlc channels each assigned to an unchannelised arbitrary rate link of up to 51.84 mhz when sysclk is running at 45 mhz. supports a mix of up to 32 channelised, unchannelised and h-mvip links, subject to the constraint of a maximum of 672 channels and a maximum aggregate link clock rate of 64 mhz in each direction. links configured for channelised t1/j1/e1 or unchannelised operation support the gapped-clock method for determining time-slots which is backwards compatible with the freedm-8 and freedm-32 devices. for each channel, the hdlc receiver supports programmable flag sequence detection, bit de-stuffing and frame check sequence validation. the receiver
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 2 supports the validation of both crc-ccitt and crc-32 frame check sequences. for each channel, the receiver che cks for packet abort sequences, octet aligned packet length and for minimum and maximum packet length. the receiver supports filtering of packets that are larger than a user specified maximum value. alternatively, for each channel, the receiver supports a transparent mode where each octet is transferred transparently to host memory. for channelised links, the octets are aligned with the receive time-slots. for each channel, time-slots are selectable to be in 56 kbits/s format or 64 kbits/s clear channel format. for each channel, the hdlc transmitter supports programmable flag sequence generation, bit stuffing and frame check sequence generation. the transmitter supports the generati on of both crc-ccitt and crc-32 frame check sequences. the transmitter also aborts packets under the direction of the host or automatically when the channel underflows. supports two levels of non-preemptive packet priority on each transmit channel. low priority packets will not beg in transmission until all high priority packets are transmitted. alternatively, for each channel, the transmitter supports a transparent mode where each octet is inserted transparently from host memory. for channelised links, the octets are aligned with the transmit time-slots. provides 32 kbytes of on-chip memory for partial packet buffering in both the transmit and receive directions. this memory may be configured to support a variety of different channel configurations from a single channel with 32 kbytes of buffering to 672 channels, each with a minimum of 48 bytes of buffering. supports pci burst sizes of up to 256 bytes for transfers of packet data. provides a standard 5 signal p1149.1 jtag test port for boundary scan board test purposes. supports 3.3 volt pci signaling environments. supports 5 volt tolerant i/o (except pci). low power 2.5 volt 0.25 m cmos technology.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 3 329 pin plastic ball grid array (pbga) package.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 4 2 applications ietf ppp interfaces for routers tdm switches frame relay interfaces for atm or frame relay switches and multiplexors funi or frame relay service inter-working interfaces for atm switches and multiplexors. internet/intranet access equipment. packet-based dslam equipment.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 5 3 references 1. international organization for standardization, iso standard 3309-1993, "information technology - telecommunications and information exchange between systems - high-level data link control (hdlc) procedures - frame structure", december 1993. 2. rfc-1662 - "ppp in hdlc-like framing" internet engineering task force, july 1994. 3. pci special interest group, pci local bus specification, june 1, 1995, version 2.1. 4. go-mvip, ?mvip-90 standard?, october 1994, release 1.1. 5. go-mvip, ?h-mvip standard?, january 1997, release 1.1a.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 6 4 application examples tdm switch fabric PM7380 freedm- 32p672 h-mvip bus pci bus packet memory pci controller bus arbite pm4354 comet-quad pm4354 comet-quad pm4354 comet-quad pm4354 comet-quad h-mvip bus t1/e1/j1 PM7380 freedm- 32p672 pci bus packet memory pci controlle r bus arbite pm8315 temux ... ds3 liu
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 7
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 8 5 block diagram r e c e i v e c h a n n e l a s s i g n e r ( r c a s 6 7 2 ) t r a n s m i t c h a n n e l a s s i g n e r ( t c a s 6 7 2 ) r e c e i v e h d l c p r o c e s s o r / p a r t i a l p a c k e t b u f f e r ( r h d l 6 7 2 ) t r a n s m i t h d l c p r o c e s s o r / p a r t i a l p a c k e t b u f f e r ( t h d l 6 7 2 ) p e r f o r m a n c e m o n i t o r ( p m o n ) r e c e i v e d m a c o n t r o l l e r ( r m a c 6 7 2 ) t r a n s m i t d m a c o n t r o l l e r ( t m a c 6 7 2 ) p c i c o n t r o l l e r ( g p i c 6 7 2 ) tbclk tbd pmctest tdo tdi tck tms trstb rbclk rbd rstb a d [ 3 1 : 0 ] c / b e b [ 3 : 0 ] p a r f r a m e b t r d y b i r d y b s t o p b d e v s e l b i d s e l l o c k b r e q b g n t b p e r r b s e r r b p c i i n t b p c i c l k p c i c l k o m 6 6 e n j t a g p o r t r d [ 3 1 : 0 ] r c l k [ 3 1 : 0 ] r f p b [ 3 : 0 ] r m v c k [ 3 : 0 ] r m v 8 d c r m v 8 f p c r f p 8 b t d [ 3 1 : 0 ] t c l k [ 3 1 : 0 ] t f p b [ 3 : 0 ] t m v c k [ 3 : 0 ] t m v 8 d c t m v 8 f p c t f p 8 b sysclk
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 9 6 description the PM7380 freedm-32p672 frame engine and datalink manager device is a monolithic integrated circuit that implements hdlc processing, and pci bus memory management functions for a maximum of 672 bi-directional channels. the freedm-32p672 may be configured to support h-mvip, channelised t1/j1/e1 or unchannelised traffic across 32 physical links. the freedm-32p672 may be configured to interface with h-mvip digital telephony buses at 2.048 mbps. for 2.048 mbps h-mvip links, the freedm- 32p672 allows up to 672 bi-directional hdlc channels to be assigned to individual time-slots within a maximum of 32 h-mvip links. the channel assignment supports the concatenation of time-slots (n x ds0) up to a maximum of 32 concatenated time-slots for each 2.048 mbps h-mvip link. time-slots assigned to any particular channel need not be contiguous within the h-mvip link. when configured for 2.048 mbps h-mvip operation, the freedm-32p672 partitions the 32 physical links into 4 logical groups of 8 links. links 0 through 7, 8 through 15, 16 through 23 and 24 through 31 make up the 4 logical groups. links in each logical group share a common clock and a common type 0 frame pulse in each direction. the freedm-32p672 may be configured to interface with h-mvip digital telephony buses at 8.192 mbps. for 8.192 mbps h-mvip links, the freedm- 32p672 allows up to 672 bi-directional hdlc channels to be assigned to individual time-slots within a maximum of 8 h-mvip links. the channel assignment supports the concatenation of time-slots (n x ds0) up to a maximum of 128 concatenated time-slots for each 8.192 h-mvip link. time-slots assigned to any particular channel need not be contiguous within the h-mvip link. when configured for 8.192 mbps h-mvip operation, the freedm-32p672 partitions the 32 physical links into 8 logical groups of 4 links. only the first link, which must be located at physical links numbered 4m (0 m 7), of each logical group can be configured for 8.192 mbps operation. the remaining 3 physical links in the logical group (numbered 4m+1, 4m+2 and 4m+3) are unused. all links configured for 8.192 mbps h-mvip operat ion will share a common type 0 frame pulse, a common frame pulse clock and a common data clock. for channelised t1/j1/e1 links, the freedm-32p672 allows up to 672 bi- directional hdlc channels to be assigned to individual time-slots within a maximum of 32 independently timed t1/j1 or e1 links. the gapped clock method to determine time-slot positions as per the freedm-8 and freedm-32 devices is retained. the channel assignment supports the concatenation of time-slots (n x ds0) up to a maximum of 24 concatenated time-slots for a t1/j1
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 10 link and 31 concatenated time-slots for an e1 link. time-slots assigned to any particular channel need not be contiguous within the t1/j1 or e1 link. for unchannelised links, the freedm-32p672 processes up to 32 bi-directional hdlc channels within 32 independently timed links. the links can be of arbitrary frame format. when limited to three unchannelised links, each link can be rated at up to 51.84 mhz provided sysclk is running at 45 mhz. for lower rate unchannelised links, the freedm-32p672 processes up to 32 links each rated at up to 10 mhz. in this case, the aggregate clock rate of all the links is limited to 64 mhz. the freedm-32p672 supports mixing of up to 32 channelised t1/j1/e1, unchannelised and h-mvip links. the total number of channels in each direction is limited to 672. the aggregate instantaneous clock rate over all 32 possible links is limited to 64 mhz. in the receive direction, the freedm-32p672 performs channel assignment and packet extraction and validation. for each provisioned hdlc channel, the freedm-32p672 delineates the packet boundaries using flag sequence detection, and performs bit de-stuffing. sharing of opening and closing flags, as well as sharing of zeros between flags are supported. the resulting packet data is placed into the internal 32 kbyte partial packet buffer ram. the partial packet buffer acts as a logical fifo for each of the assigned channels. partial packets are dma'd out of the ram, across the pci bus and into host packet memory. the freedm-32p672 validates the frame check sequence for each packet, and verifies that the packet is an integral number of octets in length and is within a programmable minimum and maximum length. the receive packet status is updated before linking the packet into a receive ready queue. the freedm- 32p672 alerts the pci host that there are packets in a receive ready queue by, optionally, asserting an interrupt on the pci bus. alternatively, in the receive direction, the freedm-32p672 supports a transparent operating mode. for each provisioned transparent channel, the freedm-32p672 directly transfers the received octets into host memory verbatim. if the transparent channel is assigned to a channelised link, then the octets are aligned to the received time-slots. in the transmit direction, the pci host provides packets to transmit using a transmit ready queue. for each provisioned hdlc channel, the freedm- 32p672 dma's partial packets across the pci bus and into the transmit partial packet buffer. the partial packets are read out of the packet buffer by the freedm-32p672 and a frame check sequence is optionally calculated and inserted at the end of each packet. bit stuffing is performed before being assigned to a particular link. the flag sequence is automatically inserted when there is no packet data for a particular channel. sequential packets are
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 11 optionally separated by two flags (an opening flag and a closing flag) or a single flag (combined opening and closing flag). zeros between flags are not shared. pci bus latency may cause one or more channels to underflow, in which case, the packets are aborted, and the host is notified. for normal traffic, an abort sequence is generated, followed by inter-fra me time fill characters (flags or all- ones bytes) until a new packet is sourced from the pci host. no attempt is made to automatically re-transmit an aborted packet. alternatively, in the transmit direction, the freedm-32p672 supports a transparent operating mode. for each provisioned transparent channel, the freedm-32p672 directly inserts the transmitted octets from host memory. if the transparent channel is assigned to a channelised link, then the octets are aligned to the transmitted time-slots. if a channel underflows due to excessive pci bus latency, an abort sequence is generated, followed by inter-frame time fill characters (flags or all-ones bytes) to indicate idle channel. data resumes immediately when the freedm-32p672 receives new data from the host. the freedm-32p672 is configured, controlled and monitored using the pci bus interface. the pci bus supports 3.3 volt signaling. the freedm-32p672 is implemented in low power 2.5 volt 0.25 m cmos technology. all non-pci freedm-32p672 i/o pins are 5 volt tolerant. the freedm-32p672 is packaged in a 329 pin plastic ball grid array (pbga) package.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 12 7 pin diagram the freedm-32p672 is manufactured in a 329 pin plastic ball grid array package. 2322212019181716151413121110987654321 a rmvck[2] rd[16] rclk[17] rclk[19] rd[21] rd[22] rd[23] rd[24] rclk[25] rclk[27] rclk[29] vdd2v5 n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c . a b rfpb[2] rclk[16] rd[18] rd[20] vdd2v5 rclk[22] rfpb[3] rclk[24] rclk[26] rd[28] rd[30] rclk[31] n.c. n.c. n.c. n.c. n.c. n.c. vdd2v5 n.c. n.c. n.c. n .c. b c rd[15] rstb rclk[15] rclk[18] rclk[20] rclk[21] rmvck[3] rd[25] rd[27] rclk[28] rclk[30] rd[31] n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c. n.c . c d rclk[13] rd[13] rclk[14] rd[17] rd[19] vdd3v3 rclk[23] vss rd[26] vdd3v3 rd[29] vss n.c. vdd3v3 n.c. vss n.c. vdd3v3 n.c. n.c. n.c. n.c. n.c. d e rd[12] vdd2v5 rclk[12] rd[14] n.c. n.c. vdd2v5 n.c. e f rd[11] rclk[10] rclk[11] vss vss n.c. n.c. n.c. f g rd[10] rd[9] rclk[8] rclk[9] bottom view pciclko pciclk n.c. pciintb g h rd[8] rmvck[1] rfpb[1] vdd3v3 vdd3v3 ad[31] reqb gntb h j rclk[7] rclk[6] rd[6] rd[7] ad[29] ad[27] ad[28] ad[30] j k sysclk rclk[5] rd[5] vss vss vss vss vss vss vss ad[24] ad[25] ad[26] k l rd[4] rd[3] rclk[3] rclk[4] vss vss vss vss vss cbeb[3] ad[22] ad[23] idsel l m vdd2v5 rclk[2] rd[2] vdd3v3 vss vss vss vss vss vdd3v3 ad[21] ad[20] vdd2v5 m n rclk[0] rd[1] rclk[1] rd[0] vss vss vss vss vss ad[16] ad[18] ad[19] ad[17] n p rmv8fpc rfpb[0] rmvck[0] vss vss vss vss vss vss vss cbeb[2] frameb irdyb p r rbd rmv8dc rfp8b rbclk stopb trdyb devselb lockb r t tck tms trstb vdd3v3 vdd3v3 perrb serrb par t u tfp8b tdo tdi tmv8dc ad[14] cbeb[1] ad[15] ad[13] u v tfpb[0] tmv8fpc tmvck[0] vss vss ad[10] ad[12] ad[11] v w td[0] vdd2v5 tclk[0] td[2] ad[6] ad[8] vdd2v5 ad[9] w y tclk[1] td[1] tclk[2] td[4] tmvck[1] vdd3v3 td[12] vss tclk[15] vdd3v3 tclk[17] vss td[22] vdd3v3 td[24] vss tclk[27] vdd3v3 tbd n.c. ad[5] cbeb[0] a d[7] y aa tclk[3] td[3] tclk[6] tfpb[1] td[9] td[10] td[13] tclk[14] tmvck[2] td[17] tclk[18] td[20] tclk[20] tclk[22] tfpb[3] td[25] tclk[26] tclk[29] tcl k[30] tbclk ad[2] ad[4] ad[3] aa ab td[5] tclk[4] tclk[7] tclk[8] vdd2v5 td[11] tclk[12] td[14] tfpb[2] tclk[16] td[19] tclk[19] td[21] td[23] tmvck[3] tclk[25] td[27] tclk[28] vdd2 v5 td[31] pmctest n.c. ad[1] ab ac tclk[5] td[6] td[7] td[8] tclk[9] tclk[10] tclk[11] tclk[13] td[15] td[16] td[18] vdd2v5 tclk[21] tclk[23] tclk[24] td[26] td[28] td[29] td[30] tc lk[31] n.c. m66en ad[0] ac 2322212019181716151413121110987654321
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 13 8 pin description table 1 ? line side interface signals (154) pin name type pin no. function rclk[0] rclk[1] rclk[2] rclk[3] rclk[4] rclk[5] rclk[6] rclk[7] rclk[8] rclk[9] rclk[10] rclk[11] rclk[12] rclk[13] rclk[14] rclk[15] rclk[16] rclk[17] rclk[18] rclk[19] rclk[20] rclk[21] rclk[22] rclk[23] rclk[24] rclk[25] rclk[26] rclk[27] rclk[28] rclk[29] rclk[30] rclk[31] input n23 n21 m22 l21 l20 k22 j22 j23 g21 g20 f22 f21 e21 d23 d21 c21 b22 a21 c20 a20 c19 c18 b18 d17 b16 a15 b15 a14 c14 a13 c13 b12 the receive line clock signals (rclk[31:0]) contain the recovered line clock for the 32 independently timed links. processing of the receive links are on a priority basis, in descending order from rclk[0] to rclk[31]. therefore, the highest rate link should be connected to rclk[0] and the lowest to rclk[31]. for channelised t1/j1 or e1 links, rclk[n] must be gapped during the framing bit (for t1/j1 interfaces) or during time-slot 0 (for e1 interfaces) of the rd[n] stream. the freedm-32p672 uses the gapping information to determine the time-slot alignment in the receive stream. rclk[31:0] is nominally a 50% duty cycle clock of frequency 1.544 mhz for t1/j1 links and 2.048 mhz for e1 links. for unchannelised links, rclk[n] must be externally gapped during the bits or time- slots that are not part of the transmission format payload (i.e. not part of the hdlc packet). rclk[2:0] is nominally a 50% duty cycle clock between 0 and 51.84 mhz. rclk[31:3] is nominally a 50% duty cycle clock between 0 and 10 mhz. the rclk[n] inputs are invalid and should be forced to a low state when their associated link is configured for operation in h-mvip mode.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 14 pin name type pin no. function rd[0] rd[1] rd[2] rd[3] rd[4] rd[5] rd[6] rd[7] rd[8] rd[9] rd[10] rd[11] rd[12] rd[13] rd[14] rd[15] rd[16] rd[17] rd[18] rd[19] rd[20] rd[21] rd[22] rd[23] rd[24] rd[25] rd[26] rd[27] rd[28] rd[29] rd[30] rd[31] input n20 n22 m21 l22 l23 k21 j21 j20 h23 g22 g23 f23 e23 d22 e20 c23 a22 d20 b21 d19 b20 a19 a18 a17 a16 c16 d15 c15 b14 d13 b13 c12 the receive data signals (rd[31:0]) contain the recovered line data for the 32 independently timed links in normal mode (pmctest set low). processing of the receive links is on a priority basis, in descending order from rd[0] to rd[31]. therefore, the highest rate link should be connected to rd[0] and the lowest to rd[31]. for h-mvip links, rd[n] contains 32/128 time-slots, depending on the h-mvip data rate configured (2.048 or 8.192 mbps). when configured for 2.048 mbps h-mvip operation, rd[31:24], rd[23:16], rd[15:8] and rd[7:0] are sampled on every 2 nd rising edge of rmvck[3], rmvck[2], rmvck[1] and rmvck[0] respectively (at the ? point of the bit interval). when configured for 8.192 mbps h-mvip operation, rd[4m] (0 m 7) are sampled on every 2 nd rising edge of rmv8dc (at the ? point of the bit interval). for channelised links, rd[n] contains the 24 (t1/j1) or 31 (e1) time-slots that comprise the channelised link. rclk[n] must be gapped during the t1/j1 framing bit position or the e1 frame alignment signal (time-slot 0). the freedm-32p672 uses the location of the gap to determine the channel alignment on rd[n]. rd[31:0] are sampled on the rising edge of the corresponding rclk[31:0]. for unchannelised links, rd[n] contains the hdlc packet data. for certain transmission formats, rd[n] may contain place holder bits or time-slots. rclk[n] must be externally gapped during the place holder positions in the rd[n] stream. the freedm-32p672 supports a maximum data rate of 10 mbit/s
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 15 pin name type pin no. function on an individual rd[31:3] link and a maximum data rate of 51.84 mbit/s on rd[2:0]. rd[31:0] are sampled on the rising edge of the corresponding rclk[31:0]. rmvck[0] rmvck[1] rmvck[2] rmvck[3] input p21 h22 a23 c17 the receive mvip data clock signals (rmvck[3:0]) provide the receive data clock for the 32 links when configured to operate in 2.048 mbps h-mvip mode. when configured for 2.048 mbps h-mvip operation, the 32 links are partitioned into 4 groups of 8, and each group of 8 links share a common data clock. rmvck[0], rmvck[1], rmvck[2] and rmvck[3] sample the data on links rd[7:0], rd[15:8], rd[23:16] and rd[31:24] respectively. each rmvck[n] is nominally a 50% duty cycle clock with a frequency of 4.096 mhz. rmvck[n] is ignored and should be tied low when no physical link within the associated logical group of 8 links is configured for operation in 2.048 mbps h-mvip mode. rfpb[0] rfpb[1] rfpb[2] rfpb[3] input p22 h21 b23 b17 the receive frame pulse signals (rfpb[3:0]) reference the beginning of each frame for the 32 links when configured for operation in 2.048 mbps h-mvip mode. when configured for 2.048 mbps h-mvip operation, the 32 links are partitioned into 4 groups of 8, and each group of 8 links share a common frame pulse. rfpb[0], rfpb[1], rfpb[2] and rfpb[3] reference the beginning of a frame on links rd[7:0], rd[15:8], rd[23:16] and rd[31:24] respectively. when configured for operation in 2.048 mbps h-mvip mode, rfpb[n] is sampled on the falling edge of rmvck[n]. otherwise, rfpb[n] is ignored and should be tied low.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 16 pin name type pin no. function rfp8b input r21 the receive frame pulse for 8.192 mbps h- mvip signal (rfp8b) references the beginning of each frame for links configured for operation in 8.192 mbps h-mvip mode. rfp8b references the beginning of a frame for any link configured for 8.192 mbps h- mvip operation. only links 4m (0 m 7) may be configured for 8.192 mbps h-mvip operation. when one or more links are configured for 8.192 mbps h-mvip operation, rfp8b is sampled on the falling edge of rmv8fpc. when no links are configured for 8.192 mbps h-mvip operation, rfp8b is ignored and should be tied low. rmv8fpc input p23 the receive 8.192 mbps h-mvip frame pulse clock signal (rmv8fpc) provides the receive frame pulse clock for links configured for operation in 8.192 mbps h- mvip mode. rmv8fpc is used to sample rfp8b. rmv8fpc is nominally a 50% duty cycle, clock with a frequency of 4.096 mhz. the falling edge of rmv8fpc must be aligned with the falling edge of rmv8dc with no more than 10 ns skew. rmv8fpc is ignored and should be tied low when no physical links are configured for operation in 8.192 mbps h-mvip mode.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 17 pin name type pin no. function rmv8dc input r22 the receive 8.192 mbps h-mvip data clock signal (rmv8dc) provides the receive data clock for links configured to operate in 8.192 mbps h-mvip mode. rmv8dc is used to sample data on rd[4m] (0 m 7) when link 4m is configured for 8.192 mbps h-mvip operation. rmv8dc is nominally a 50% duty cycle clock with a frequency of 16.384 mhz. rmv8dc is ignored and should be tied low when no physical links are configured for operation in 8.192 mbps h-mvip mode. rbd tristate output r23 the receive bert data signal (rbd) contains the receive bit error rate test data. rbd reports the data on the selected one of the receive data signals (rd[31:0]) and is updated on the falling edge of rbclk. rbd may be tristated by setting the rben bit in the freedm-32p672 master bert control register low. bert is not supported for h-mvip links. rbclk tristate output r20 the receive bert clock signal (rbclk) contains the receive bit error rate test clock. rbclk is a buffered version of the selected one of the receive clock signals (rclk[31:0]). rbclk may be tristated by setting the rben bit in the freedm- 32p672 master bert control register low. bert is not supported for h-mvip links.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 18 pin name type pin no. function tclk[0] tclk[1] tclk[2] tclk[3] tclk[4] tclk[5] tclk[6] tclk[7] tclk[8] tclk[9] tclk[10] tclk[11] tclk[12] tclk[13] tclk[14] tclk[15] tclk[16] tclk[17] tclk[18] tclk[19] tclk[20] tclk[21] tclk[22] tclk[23] tclk[24] tclk[25] tclk[26] tclk[27] tclk[28] tclk[29] tclk[30] tclk[31] input w21 y23 y21 aa23 ab22 ac23 aa21 ab21 ab20 ac19 ac18 ac17 ab17 ac16 aa16 y15 ab14 y13 aa13 ab12 aa11 ac11 aa10 ac10 ac9 ab8 aa7 y7 ab6 aa6 aa5 ac4 the transmit line clock signals (tclk[31:0]) contain the transmit clocks for the 32 independently timed links. processing of the transmit links is on a priority basis, in descending order from tclk[0] to tclk[31]. therefore, the highest rate link should be connected to tclk[0] and the lowest to tclk[31]. for channelised t1/j1 or e1 links, tclk[n] must be gapped during the framing bit (for t1/j1 interfaces) or during time-slot 0 (for e1 interfaces) of the td[n] stream. the freedm-32p672 uses the gapping information to determine the time-slot alignment in the transmit stream. for unchannelised links, tclk[n] must be externally gapped during the bits or time- slots that are not part of the transmission format payload (i.e. not part of the hdlc packet). tclk[2:0] is nominally a 50% duty cycle clock between 0 and 51.84 mhz. tclk[31:3] is nominally a 50% duty cycle clock between 0 and 10 mhz. typical values for tclk[31:0] include 1.544 mhz (for t1/j1 links) and 2.048 mhz (for e1 links). the tclk[n] inputs are invalid and should be tied low when their associated link is configured for operation in h-mvip mode.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 19 pin name type pin no. function td[0] td[1] td[2] td[3] td[4] td[5] td[6] td[7] td[8] td[9] td[10] td[11] td[12] td[13] td[14] td[15] td[16] td[17] td[18] td[19] td[20] td[21] td[22] td[23] td[24] td[25] td[26] td[27] td[28] td[29] td[30] td[31] output w23 y22 w20 aa22 y20 ab23 ac22 ac21 ac20 aa19 aa18 ab18 y17 aa17 ab16 ac15 ac14 aa14 ac13 ab13 aa12 ab11 y11 ab10 y9 aa8 ac8 ab7 ac7 ac6 ac5 ab4 the transmit data signals (td[31:0]) contain the transmit data for the 32 independently timed links in normal mode (pmctest set low). processing of the transmit links is on a priority basis, in descending order from td[0] to td[31]. therefore, the highest rate link should be connected to td[0] and the lowest to td[31]. for h-mvip links, td[n] contain 32/128 time-slots, depending on the h-mvip data rate configured (2.048 or 8.192 mbps). when configured for 2.048 mbps h-mvip operation, td[31:24], td[23:16], td[15:8] and td[7:0] are updated on every 2 nd falling edge of tmvck[3], tmvck[2], tmvck[1] and tmvck[0] respectively. when configured for 8.192 mbps h-mvip operation, td[4m] (0 m 7) are updated on every 2 nd falling edge of tmv8dc. for channelised links, td[n] contains the 24 (t1/j1) or 31 (e1) time-slots that comprise the channelised link. tclk[n] must be gapped during the t1/j1 framing bit position or during the e1 frame alignment signal (time-slot 0). the freedm-32p672 uses the location of the gap to determine the channel alignment on td[n]. td[31:0] are updated on the fallin g edge of the corresponding tclk[31:0]. for unchannelised links, td[n] contains the hdlc packet data. for certain transmission formats, td[n] may contain place holder bits or time-slots. tclk[n] must be externally gapped during the place holder positions in the td[n] stream. the freedm-32p672 supports a maximum data rate of 10 mbit/s on an individual td[31:3] link and a maximum data rate of 51.84 mbit/s on td[2:0].
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 20 pin name type pin no. function td[31:0] are updat ed on the fallin g edge of the corresponding tclk[31:0] clock. tmvck[0] tmvck[1] tmvck[2] tmvck[3] input v21 y19 aa15 ab9 the transmit mvip data clock signals (tmvck[3:0]) provide the transmit data clocks for the 32 links when configured to operate in 2.048 mbps h-mvip mode. when configured for 2.048 mbps h-mvip operation, the 32 links are partitioned into 4 groups of 8, and each group of 8 links share a common clock. tmvck[0], tmvck[1], tmvck[2] and tmvck[3] update the data on links td[7:0], td[15:8], td[23:16] and td[31:24] respectively. each tmvck[n] is nominally a 50% duty cycle clock with a frequency of 4.096 mhz. tmvck[n] is ignored and should be tied low when no physical link within the associated group of 8 logical links is configured for operation in 2.048 mbps h-mvip mode. tfpb[0] tfpb[1] tfpb[2] tfpb[3] input v23 aa20 ab15 aa9 the transmit frame pulse signals (tfpb[3:0]) reference the beginning of each frame when configured for operation in 2.048 mbps h-mvip mode. when configured for 2.048 mbps h-mvip operation, the 32 links are partitioned into 4 groups of 8, and each group of 8 links share a common frame pulse. tfpb[0], tfpb[1], tfpb[2] and tfpb[3] reference the beginning of a frame on links td[7:0], td[15:8], td[23:16] and td[31:24] respectively. when configured for operation in 2.048 mbps h-mvip mode, tfpb[n] is sampled on the falling edge of tmvck[n]. otherwise, tfpb[n] is ignored and should be tied low.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 21 pin name type pin no. function tfp8b input u23 the transmit frame pulse for 8.192 mbps h- mvip signal (tfp8b) references the beginning of each frame for links configured to operate in 8.192 mbps h-mvip mode. tfp8b references the beginning of a frame for any link configured for 8.192 mbps h- mvip operation. only links 4m (0 m 7) may be configured for 8.192 mbps h-mvip operation. when one or more links are configured for 8.192 mbps h-mvip operation, tfp8b is sampled on the falling edge of tmv8fpc. when no links are configured for 8.192 mbps h-mvip operation, tfpb[n] is ignored and should be tied low. tmv8fpc input v22 the transmit 8.192 mbps h-mvip frame pulse clock signal (tmv8fpc) provides the transmit frame pulse clock for links configured for operation in 8.192 mbps h- mvip mode. tmv8fpc is used to sample tfp8b. tmv8fpc is nominally a 50% duty cycle, clock with a frequency of 4.096 mhz. the falling edge of tmv8fpc must be aligned with the falling edge of tmv8dc with no more than 10 ns skew. tmv8fpc[n] is ignored and should be tied low when no physical links are configured for operation in 8.192 mbps h-mvip mode.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 22 pin name type pin no. function tmv8dc input u20 the transmit 8.192 mbps h-mvip data clock signal (tmv8dc) provides the transmit data clock for links configured to operate in 8.192 mbps h-mvip mode. tmv8dc is used to update data on td[4m] (0 m 7) when link 4m is configured for 8.192 mbps h-mvip operation. tmv8dc is nominally a 50% duty cycle clock with a frequency of 16.384 mhz. tmv8dc is ignored and should be tied low when no physical links are configured for operation in 8.192 mbps h-mvip mode. tbd input y5 the transmit bert data signal (tbd) contains the transmit bit error rate test data. when the tberten bit in the bert control register is set high, the data on tbd is transmitted on the selected one of the transmit data signals (td[31:0]). tbd is sampled on the rising edge of tbclk. bert is not supported for h-mvip links. tbclk tristate output aa4 the transmit bert clock signal (tbclk) contains the transmit bit error rate test clock. tbclk is a buffered version of the selected one of the transmit clock signals (tclk[31:0]). tbclk may be tristated by setting the tben bit in the freedm- 32p672 master bert control register low. bert is not supported for h-mvip links.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 23 table 2 ? pci host interface signals (52) pin name type pin no. function pciclk input g3 the pci clock signal (pciclk) provides timing for pci bus accesses. pciclk is a nominally 50% duty cycle, 25 to 66 mhz clock. pciclko output g4 the pci clock output signal (pciclko) is a buffered version of the pciclk. pciclko may be used to derive the sysclk input. c/beb[0] c/beb[1] c/beb[2] c/beb[3] i/o y2 u3 p3 l4 the pci bus command and byte enable bus (c/beb[3:0]) contains the bus command or the byte valid indications. during the first clock cycle of a transaction, c/beb[3:0] contains the bus command code. for subsequent clock cycles, c/beb[3:0] identifies which bytes on the ad[31:0] bus carry valid data. c/beb[3] is associated with byte 3 (ad[31:24]) while c/beb[0] is associated with byte 0 (ad[7:0]). when c/beb[n] is set high, the associated byte is invalid. when c/beb[n] is set low, the associated byte is valid. when the freedm-32p672 is the initiator, c/beb[3:0] is an output bus. when the freedm-32p672 is the target, c/beb[3:0] is an input bus. when the freedm-32p672 is not involved in the current transaction, c/beb[3:0] is tristated. as an output bus, c/beb[3:0] is updated on the rising edge of pciclk. as an input bus, c/beb[3:0] is sampled on the rising edge of pciclk.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 24 pin name type pin no. function ad[0] ad[1] ad[2] ad[3] ad[4] ad[5] ad[6] ad[7] ad[8] ad[9] ad[10] ad[11] ad[12] ad[13] ad[14] ad[15] ad[16] ad[17] ad[18] ad[19] ad[20] ad[21] ad[22] ad[23] ad[24] ad[25] ad[26] ad[27] ad[28] ad[29] ad[30] ad[31] i/o ac1 ab1 aa3 aa1 aa2 y3 w4 y1 w3 w1 v3 v1 v2 u1 u4 u2 n4 n1 n3 n2 m2 m3 l3 l2 k3 k2 k1 j3 j2 j4 j1 h3 the pci address and data bus (ad[31:0]) carries the pci bus multiplexed address and data. during the first clock cycle of a transaction, ad[31:0] contains a physical byte address. during subsequent clock cycles of a transaction, ad[31:0] contains data. a transaction is defined as an address phase followed by one or more data phases. when little-endian byte formatting is selected, ad[31:24] contain the most significant byte of a dword while ad[7:0] contain the least significant byte. when big-endian byte formatting is selected. ad[7:0] contain the most significant byte of a dword while ad[31:24] contain the least significant byte. when the freedm-32p672 is the initiator, ad[31:0] is an output bus during the first (address) phase of a transaction. for write transactions, ad[31:0] remains an output bus for the data phases of the transaction. for read transactions, ad[31:0] is an input bus during the data phases. when the freedm-32p672 is the target, ad[31:0] is an input bus during the first (address) phase of a transaction. for write transactions, ad[31:0] remains an input bus during the data phases of the transaction. for read transactions, ad[31:0] is an output bus during the data phases. when the freedm-32p672 is not involved in the current transaction, ad[31:0] is tristated. as an output bus, ad[31:0] is updated on the rising edge of pciclk. as an input bus, ad[31:0] is sampled on the rising edge of pciclk.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 25 pin name type pin no. function par i/o t1 the parity signal (par) indicates the parity of the ad[31:0] and c/beb[3:0] buses. even parity is calculated over all 36 signals in the buses regardless of whether any or all the bytes on the ad[31:0] are valid. par always reports the parity of the previous pciclk cycle. parity errors detected by the freedm-32p672 are indicated on output perrb and in the freedm-32p672 interrupt status register. when the freedm-32p672 is the initiator, par is an output for writes and an input for reads. when the freedm-32p672 is the target, par is an input for writes and an output for reads. when the freedm-32p672 is not involved in the current transaction, par is tristated. as an output signal, par is updated on the rising edge of pciclk. as an input signal, par is sampled on the rising edge of pciclk. frameb i/o p2 the active low cy cle frame signal (frameb) identifies a transaction cycle. when frameb transitions low, the start of a bus transaction is indicated. frameb remains low to define the duration of the cycle. when frameb transitions high, the last data phase of the current transaction is indicated. when the freedm-32p672 is the initiator, frameb is an output. when the freedm-32p672 is the target, frameb is an input. when the freedm-32p672 is not involved in the current transaction, frameb is tristated. as an output signal, frameb is updated on the rising edge of pciclk. as an input signal, frameb is sampled on the rising edge of pciclk.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 26 pin name type pin no. function trdyb i/o r3 the active low target ready signal (trdyb) indicates when the target is ready to start or continue with a transaction. trdyb works in conjunction with irdyb to complete transaction data phases. during a transaction in progress, trdyb is set high to indicate that the target cannot complete the current data phase and to force a wait state. trdyb is set low to indicate that the target can complete the current data phase. the data phase is completed when trdyb is set low and the initiator ready signal (irdyb) is also set low. when the freedm-32p672 is the initiator, trdyb is an input. when the freedm-32p672 is the target, trdyb is an output. during accesses to freedm-32p672 registers, trdyb is set high to extend data phases over multiple pciclk cycles. when the freedm-32p672 is not involved in the current transaction, trdyb is tristated. as an output signal, trdyb is updated on the rising edge of pciclk. as an input signal, trdyb is sampled on the rising edge of pciclk.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 27 pin name type pin no. function irdyb i/o p1 the active low initiator ready (irdyb) signal is used to indicate whether the initiator is ready to start or continue with a transaction. irdyb works in conjunction with trdyb to complete transaction data phases. when irdyb is set high and a transaction is in progress, the initiator is indicating it cannot complete the current data phase and is forcing a wait state. when irdyb is set low and a transaction is in progress, the initiator is indicating it has completed the current data phase. the data phase is completed when irdyb is set low and the target ready signal (irdyb) is also set low. when the freedm-32p672 is the initiator, irdyb is an output. when the freedm-32p672 is the target, irdyb is an input. when the freedm-32p672 is not involved in the current transaction, irdyb is tristated. irdyb is updated on the rising edge of pciclk or sampled on the rising edge of pciclk depending on whether it is an output or an input.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 28 pin name type pin no. function stopb i/o r4 the active low stop signal (stopb) requests the initiator to stop the current bus transaction. when stopb is set high by a target, the initiator continues with the transaction. when stopb is set low, the initiator will stop the current transaction. when the freedm-32p672 is the initiator, stopb is an input. when stopb is sampled low, the freedm-32p672 will terminate the current transaction in the next pciclk cycle. when the freedm-32p672 is the target, stopb is an output. the freedm-32p672 only issues transaction stop requests when responding to reads and writes to configuration space (disconnecting after 1 dword transferred) or if an initiator introduces wait states during a transaction. when the freedm-32p672 is not involved in the current transaction, stopb is tristated. stopb is updated on the rising edge of pciclk or sampled on the rising edge of pciclk depending on whether it is an output or an input. idsel input l1 the initialization device select signal (idsel) enables read and write access to the pci configuration registers. when idsel is set high during the address phase of a transaction and the c/beb[3:0] code indicates a register read or write, the freedm-32p672 performs a pci configuration register transaction and asserts the devselb signal in the next pciclk period. idsel is sampled on the rising edge of pciclk.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 29 pin name type pin no. function devselb i/o r2 the active low dev ice select signal (devselb) indicates that a target claims the current bus transaction. during the address phase of a transaction, all targets decode the address on the ad[31:0] bus. when a target, recognizes the address as its own, it sets devselb low to indicate to the initiator that the address is valid. if no target claims the address in six bus clock cycles, the initiator assumes that the target does not exist or cannot respond and aborts the transaction. when the freedm-32p672 is the initiator, devselb is an input. if no target responds to an address in six pciclk cycles, the freedm- 32p672 will abort the curr ent transaction and alerts the pci host via an interrupt. when the freedm-32p672 is the target, devselb is an output. delselb is set low when the address on ad[31:0] is recognised. when the freedm-32p672 is not involved in the current transaction, devselb is tristated. freedm-32p672 is updated on the rising edge of pciclk or sampled on the rising edge of pciclk depending on whether it is an output or an input. lockb input r1 the active low bus lock signal (lockb) locks a target device. when lockb and frame are set low, and the freedm-32p672 is the target, an initiator is locking the freedm-32p672 as an "owned" target. under these circumstances, the freedm-32p672 will re ject all transaction with other initiators. the freedm-32p672 will continue to reject other initiators until its owner releases the lock by forcing both frameb and lockb high. as a initiator, the freedm- 32p672 will never lock a target. lockb is sampled using the rising edge of pciclk.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 30 pin name type pin no. function reqb tristate output h2 the active low pci bus request signal (reqb) requests an external arbiter for control of the pci bus. reqb is set low when the freedm- 32p672 desires access to the host memory. reqb is set high when access is not desired. reqb is updated on the rising edge of pciclk. gntb input h1 the active low pci bus grant signal (gntb) indicates the granting of control over the pci in response to a bus request via the reqb output. when gntb is set high, the freedm-32p672 does not have control over the pci bus. when gntb is set low, the external arbiter has granted the freedm-32p672 control over the pci bus. however, the freedm-32p672 will not proceed until the frameb signal is sampled high, indicating no current transactions are in progress. gntb is sampled on the rising edge of pciclk. pciintb od output g1 the active low pci inte rrupt signal (pciintb) is set low when a freedm-32p672 interrupt source is active, and that source is unmasked. the freedm-32p672 may be enabled to report many alarms or events via interrupts. pciintb returns high when the interrupt is acknowledged via an appropriate register access. pciintb is an open drain output and is asynchronous to pciclk.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 31 pin name type pin no. function perrb i/o t3 the active low parity error signal (perrb) indicates a parity error over the ad[31:0] and c/beb[3:0] buses. parity error is signalled when even parity calculations do not match the par signal. perrb is set low at the cycle immediately following an offending par cycle. perrb is set high when no parity error is detected. perrb is enabled by setting the perren bit in the control/status register in the pci configuration registers space. regardless of the setting of perren, parity errors are always reported by the perr bit in the control/status register in the pci configuration registers space. perrb is updated on the rising edge of pciclk. serrb od output t2 the active low system error signal (serrb) indicates an address parity error. address parity errors are detected when the even parity calculations during the address phase do not match the par signal. when the freedm- 32p672 detects a system error, serrb is set low for one pciclk period. serrb is enabled by setting the serren bit in the control/status register in the pci configuration registers space. regardless of the setting of serren, parity errors are always reported by the serr bit in the control/status register in the pci configuration registers space. serrb is an open drain output and is updated on the rising edge of pciclk. m66en input ac2 the active high 66 mhz mode enable signal (m66en) reflects the speed of operation of the pci bus. m66en should be set high for 66 mhz operation on the pci bus. m66en should be set low for 33 mhz operation on the pci bus.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 32 table 3 ? miscellaneous interface signals (58) pin name type pin no. function sysclk input k23 the system clock (sysclk) provides timing for the core logic. sysclk is nominally a 50% duty cycle, 25 to 45 mhz clock. rstb input c22 the active low reset signal (rstb) signal provides an asynchronous freedm-32p672 reset. rstb is an asynchronous input. when rstb is set low, all freedm-32p672 registers are forced to their default states. in addition, td[31:0] are forced high and all pci output pins are forced tristate and will remain high or tristated, respectively, until rstb is set high. pmctest input ab3 the pmc production test enable signal (pmctest) places the freedm-32p672 is test mode. when pmctest is set high, production test vectors can be executed to verify manufacturing via the test mode interface signals ta[11:0], ta[12]/trs, trdb, twrb and tdat[15:0]. pmctest must be tied low for normal operation. tck input t23 the test clock signal (tck) provides timing for test operations that can be carried out using the ieee p1149.1 test access port. tms and tdi are sampled on the rising edge of tck. tdo is updated on the falling edge of tck. tms input t22 the test mode select signal (tms) controls the test operations that can be carried out using the ieee p1149.1 test access port. tms is sampled on the rising edge of tck. tms has an integral pull up resistor. tdi input u21 the test data input signal (tdi) carries test data into the freedm-32p672 via the ieee p1149.1 test access port. tdi is sampled on the rising edge of tck. tdi has an integral pull up resistor.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 33 pin name type pin no. function tdo tristate output u22 the test data output signal (tdo) carries test data out of the freedm-32p672 via the ieee p1149.1 test access port. tdo is updated on the falling edge of tck. tdo is a tristate output which is inactive except when scanning of data is in progress. trstb input t21 the active low test reset signal (trstb) provides an asynchronous freedm-32p672 test access port reset via the ieee p1149.1 test access port. trstb is an asynchronous input with an integral pull up resistor. note that when trstb is not being used, it must be connected to the rstb input. nc1-50 open these pins must be left unconnected. table 4 ? production test interf ace signals (0 - multiplexed) pin name type pin no. function ta[0] ta[1] ta[2] ta[3] ta[4] ta[5] ta[6] ta[7] ta[8] ta[9] ta[10] ta[11] input g23 f23 e23 d22 e20 c23 a22 d20 b21 d19 b20 a19 the test mode address bus (ta[11:0]) selects specific registers during production test (pmctest set high) read and write accesses. ta[11:0] replace rd[21:10] when pmctest is set high. ta[12]/tr s input a16 the test register select signal (ta[12]/trs) selects between normal and test mode register accesses during production test (pmctest set high). trs is set high to select test registers and is set low to select normal registers. ta[12]/trs replaces rd[24] when pmctest is set high.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 34 pin name type pin no. function trdb input a18 the test mode read enable signal (trdb) is set low during freedm-32p672 register read accesses during production test (pmctest set high). the freedm-32p672 drives the test data bus (tdat[15:0]) with the contents of the addressed register while trdb is low. trdb replaces rd[22] when pmctest is set high. twrb input a17 the test mode write enable signal (twrb) is set low during freedm-32p672 register write accesses during production test (pmctest set high). the contents of the test data bus (tdat[15:0]) are clocked into the addressed register on the rising edge of twrb. twrb replaces rd[23] when pmctest is set high. tdat[0] tdat[1] tdat[2] tdat[3] tdat[4] tdat[5] tdat[6] tdat[7] tdat[8] tdat[9] tdat[10] tdat[11] tdat[12] tdat[13] tdat[14] tdat[15] i/o ac1 4 aa14 ac1 3 ab13 aa12 ab11 y11 ab10 y9 aa8 ac8 ab7 ac7 ac6 ac5 ab4 the bi-directional test mode data bus (tdat[15:0]) carries data read from or written to freedm-32p672 registers during production test. tdat[15:0] replace td[31:16] when pmctest is set high.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 35 table 5 ? power and ground signals (65) pin name type pin no. function vdd3v3[1] vdd3v3[2] vdd3v3[3] vdd3v3[4] vdd3v3[5] vdd3v3[6] vdd3v3[7] vdd3v3[8] vdd3v3[9] vdd3v3[10] vdd3v3[11] vdd3v3[12] vdd3v3[13] vdd3v3[14] power d6 d10 d14 d18 h4 h20 m4 m20 t4 t20 y6 y10 y14 y18 the vdd3v3[14:1] dc power pins should be connected to a well decoupled +3.3 v dc supply. these power pins provide dc current to the i/o pads. vdd2v5[1] vdd2v5[2] vdd2v5[3] vdd2v5[4] vdd2v5[5] vdd2v5[6] vdd2v5[7] vdd2v5[8] vdd2v5[9] vdd2v5[10] vdd2v5[11] vdd2v5[12] power e2 m1 w2 ab5 ac1 2 ab19 w22 m23 e22 b19 a12 b5 the vdd2v5[12:1] dc power pins should be connected to a well decoupled +2.5 v dc supply. these power pins provide dc current to the digital core.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 36 pin name type pin no. function vss[1] vss[2] vss[3] vss[4] vss[5] vss[6] vss[7] vss[8] vss[9] vss[10] vss[11] vss[12] vss[13] vss[14] ground d8 d12 d16 f4 f20 k4 k20 p4 p20 v4 v20 y8 y12 y16 the vss[14:1] dc ground pins should be connected to ground. they provide a ground reference for the 3.3 v rail. they also provide a ground reference for the 2.5 v rail. vss[15] vss[16] vss[17] vss[18] vss[19] vss[20] vss[21] vss[22] vss[23] vss[24] vss[25] vss[26] vss[27] vss[28] vss[29] vss[30] vss[31] vss[32] vss[33] vss[34] vss[35] vss[36] vss[37] vss[38] vss[39] k10 k11 k12 k13 k14 l10 l11 l12 l13 l14 m10 m11 m12 m13 m14 n10 n11 n12 n13 n14 p10 p11 p12 p13 p14 the vss[39:15] dc ground pins should be connected to ground. they provide improved thermal properties for the 329 pbga package.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 37 notes on pin description: 1. all freedm-32p672 non-pci inputs and bi-directionals present minimum capacitive loading and are 5 volt tolerant. pci signals conform to the 3.3 volt signaling environment. 2. all freedm-32p672 non-pci outputs and bi-directionals have 4 ma drive capability, except the pciclko, rbclk, tbclk and rbd outputs which have 8 ma drive capability. 3. all freedm-32p672 outputs can be tristated under control of the ieee p1149.1 test access port, even those which do not tristate under normal operation. all non-pci outputs and bi-directionals are 5 v tolerant when tristated. 4. all non-pci inputs are schmitt triggered. inputs tms, tdi and trstb have internal pull-up resistors. 5. power to the vdd3v3 pins should be applied before power to the vdd2v5 pins is applied. similarly, power to the vdd2v5 pins should be removed before power to the vdd3v3 pins is removed.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 38 9 functional description 9.1 high speed multi-vendor in tegration protocol (h-mvip) h-mvip defines a synchronous, time division multiplexed (tdm) bus of nx64 kbps constant bit rate (cbr) data streams. each 64 kbps data stream (time- slot) carries an 8-bit byte of hdlc traffic, as described in the following section, and is characterised by 8 khz framing. h-mvip supports higher bandwidth applications on existing telephony networks by fitting more time-slots into a 125 s frame. the freedm-32p672 supports h-mvip data rates of 2.048 mbps and 8.192 mbps with 32 or 128 time-slots per frame and associated clocking frequencies of 4.096 and 16.384 mhz respectively. figure 1 shows a diagram of the h-mvip protocol supported by the freedm-32p672 device. figure 1 ? h-mvip protocol data clock (4, 16 mhz) frame pulse (8 khz) serial data b8 b1 b2 b8 ts 31/127 ts 0 ts 1 b1 ts 31/127 b2 b8 b7 125 us frame pulse clock (4 mhz) b7 9.2 high-level data link control (hdlc) protocol figure 2 shows a diagram of the synchronous hdlc protocol supported by the freedm-32p672 device. the incoming stream is examined for flag bytes (01111110 bit pattern) which deli neate the opening and closing of the hdlc packet. the packet is bit de-stuffed which discards a "0" bit which directly follows five contiguous "1" bits. the resulting hdlc packet size must be a multiple of an octet (8 bits) and within the expected minimum and maximum packet length limits. the minimum packet length is that of a packet containing two information bytes (address and control) and fcs bytes. for packets with crc-ccitt as fcs, the minimum packet length is four bytes while those with crc-32 as fcs, the minimum length is six bytes. an hdlc packet is aborted when seven contiguous "1" bits (with no inserted "0" bits) are received. at least
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 39 one flag byte must exist between hdlc packets for delineation. contiguous flag bytes, or all ones bytes between packets ar e used as an "inter-frame time fill". adjacent flag bytes may share zeros. figure 2 ? hdlc frame flag information fcs flag hdlc packet flag the crc algorithm for the frame checking sequence (fcs) field is either a crc-ccitt or crc-32 function. figure 3 shows a crc encoder block diagram using the generating polynomial g(x) = 1 + g 1 x + g 2 x 2 +?+ g n-1 x n-1 + x n . the crc-ccitt fcs is two bytes in size and has a generating polynomial g(x) = 1 + x 5 + x 12 + x 16 . the crc-32 fcs is four byte s in size and has a generating polynomial g(x) = 1 + x + x 2 + x 4 + x 5 + x 7 + x 8 + x 10 + x 11 + x 12 + x 16 + x 22 + x 23 + x 26 + x 32 . the first fcs bit received is the residue of the highest term. figure 3 ? crc generator d 0 d 1 g 1 d 2 d n-1 message parity check digits g 2 g n-1 lsb msb 9.3 receive channel assigner the receive channel assigner block (rcas672) processes up to 32 serial links. links may be configured to support 2.048 or 8.192 mbps h-mvip traffic, to support t1/j1/e1 channelised traffic or to support unchannelised traffic. when configured to support 2.048 mbps h-mvip traffic, each group of 8 links share a clock and frame pulse. all links configured for 8.192 mbps h-mvip traffic share a common clock and frame pulse. for t1/j1/e1 channelised traffic or for unchannelised traffic, each link is independent and has its own associated clock. for each link, the rcas672 performs a serial to parallel conversion to form data bytes. the data bytes are multiplexed, in byte serial format, for delivery to the receive hdlc processor / partial packet buffer block (rhdl672) at sysclk
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 40 rate. in the event where multiple streams have accumulated a byte of data, multiplexing is performed on a fixed priority basis with link #0 having the highest priority and link #31 the lowest. from the point of view of the rcas672, links configured for h-mvip traffic behave identically to links configured for t1/j1/e1 channelised or unchannelised traffic in the back end, only differing on the link side as described herein. first, the number of time-slots in each frame is programmable to be 32 or 128 and has an associated data clock frequency that is double the data rate. this provides more bandwidth per link for applications requiring higher data densities on a single link. second, h-mvip links reference the start of each frame with a frame pulse, thereby avoiding having to gap the link clock during the framing bits/bytes of each frame. the frame pulse is provided by an h-mvip bus master and ensures that all agents sharing the h-mvip bus remain synchronized. when configured for operation in 2.048 mbps mode, the frame pulse is sampled using the same clock which samples the data. when configured for operation in 8.192 mbps h-mvip mode, the frame pulse is sampled using a separate frame pulse clock provided by an h-mvip bus master. the frame pulse clock has a synchronous timing relationship to the data clock. third, not all links are independent. when configured for operation in 2.048 mbps h-mvip mode, each group of 8 links share a clock and a frame pulse. links 0 through 7, 8 through 15, 16 through 23 and 24 through 31 each share a clock and a frame pulse. not all 8 links within each group need to be configured for operation in 2.048 mbps h-mvip mode. however, any link within each logical group of 8 which is configured for 2.048 mbps h-mvip oper ation will share the same clock and frame pulse. when configured for operation in 8.192 mbps h-mvip mode, links 4m (0 m 7) share a frame pulse, a data clock and a frame pulse clock. again, not all eight 4m (0 m 7) links need to be configured for operation in 8.192 mbps h-mvip mode, however, any link which is configured for 8.192 mbps h-mvip operation will share the same frame pulse, data clock and frame pulse clock. if link 4m is configured for 8.192 mbps h-mvip operation, then data transferred on that link is ?spread? over links 4m, 4m+1, 4m+2 and 4m+3 from a channel assigner point of view. accordingly, when link 4m is configured for operation in 8.192 mbps h-mvip mode, links 4m+1, 4m+2 and 4m+3 must also be configured for operation in 8.192 mbps h-mvip mode. in the back end, the rcas672 extracts and processes the time-slots in the same way as channelised t1/j1/e1 traffic. links containing a t1/j1 or an e1 stream may be channelised. data at each time-slot may be independently assigned to a different channel. the rcas672 performs a table lookup to associate the link and time-slot identity with a channel. t1/j1 and e1 framing bits/bytes are identified by observing the gap in the link clock which is squelched during the framing bits/bytes. for unchannelised links, clock rates are limited to 51.84 mhz for links #0 to #2 and limited to 10 mhz for the remaining links. all data on each link belongs to one
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 41 channel. for the case of a mixture of channelised, unchannelised and h-mvip links, the total instantaneous link rate over all the links is limited to 64 mhz. the rcas672 performs a table lookup using only the link number to determine the associated channel, as time-slots are non-existent in unchannelised links. the rcas672 provides diagnostic loopback that is selectable on a per channel basis. the rcas672 does not support diagnostic loopback for links configured as h-mvip. when a channel is in diagnostic loopback, stream data on the received links originally destined for that channel is ignored. transmit data of that channel is substituted in its place. 9.3.1 line interface translator (lit) the lit block translates the information on the 32 physical links into a suitable format for interpretation by the line interface block. the lit block performs three functions: data translation, clock translation and frame pulse generation. when link 4m (0 m 7) is configured for operation in 8.192 mbps h-mvip mode, the lit block translates the 128 time-slots on link 4m to the line interface block across links 4m, 4m+1, 4m+2 and 4m+3. the lit block provides time-slots 0 through 31, 32 through 63, 64 through 95 and 96 through 127 to the line interface block on links 4m, 4m+1, 4m+2 and 4m+3 respectively. when link 4m is configured for operation in 8.192 mbps h-mvip mode, data cannot be received on inputs rd[4m+3:4m+1]. however, links 4m+1, 4m+2 and 4m+3 must be programmed in the rcas672 link configuration register for 8.192 mbps h-mvip operation. when links are configured for operation in 2.048 mbps h- mvip mode, channelised t1/j1/e1 mode or unchannelised mode, the lit block does not perform any translation on the link data. when a link is configured for operation in h-mvip mode, the lit block divides the appropriate clock (rmvck[n] for 2.048 mbps h-mvip and rmv8dc for 8.192 mbps h-mvip) by two and provides this divided down clock to the line interface block. when a link is configured for operation in channelised t1/j1/e1 or unchannelised mode, the lit block does not perform any translation on the link clock. when a link is configured for operation in h-mvip mode, the lit block samples the appropriate frame pulse (rfpb[n] for 2.048 mbps h-mvip and rfp8b for 8.192 mbps h-mvip) and presents the sampled frame pulse to the line interface block. when a link is configured for operation in channelised t1/j1/e1 or unchannelised mode, the gapped clock is passed to the lit block unmodified.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 42 9.3.2 line interface there are 32 identical line interface blocks in the rcas672. each line interface block contains 2 sub-bl ocks; one supporting channelised t1/j1/e1 streams and the other h-mvip streams. based on c onfiguration, only one of the sub-blocks are active at one time; the other is held reset. each sub-block contains a bit counter, an 8-bit shift register and a holding register. each sub-block performs serial to parallel conversion. whenever the holding register is updated, a request for service is sent to the priority encoder block. when acknowledged by the priority encoder, the line interface would respond with the data residing in the holding register in the active sub-block. to support h-mvip links, each line interface block contains a time-slot counter. the time-slot counter is incremented each time the holding register is updated. when a frame pulse occurs, the time-slot counter is initialised to indicate that the next bit is the most significant bit of the first time-slot. to support non h-mvip channelised links, each line interface block contains a time-slot counter and a clock activity monitor. the time-slot counter is incremented each time the holding register is updated. the clock activity monitor is a counter that increments at the system clock (sysclk) rate and is cleared by a rising edge of the receive clock (rclk[n]). a framing bit (t1/j1) or a framing byte (e1) is detected when the counter reaches a programmable threshold, in which case, the bit and time-slot counters are initialised to indicate that the next bit is the most significant bit of the first time-slot. for unchannelised links, the time-slot counter and the clock activity monitor are held reset. 9.3.3 priority encoder the priority encoder monitors the line interfaces for requests and synchronises them to the sysclk timing domain. requests are serviced on a fixed priority scheme where highest to lowest priority is assigned from the line interface attached to rd[0] to that attached to rd[31]. thus, simultaneous requests from rd[m] will be serviced ahead of rd[n], if m < n. when there are no pending requests, the priority encoder generates an idle cycle. in addition, once every fourth sysclk cycle, the priority encoder inserts a null cycle where no requests are serviced. this cycle is used by the channel assigner downstream for host microprocessor accesses to the provisioning rams. 9.3.4 channel assigner the channel assigner block determines the channel number of the data byte currently being processed. the block contains a 1024 word channel provision ram. the address of the ram is constructed from concatenating the link
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 43 number and the time-slot number of the current data byte. the fields of each ram word include the channel number and a time-slot enable flag. the time-slot enable flag labels the current time-slot as belonging to the channel indicted by the channel number field. 9.3.5 loopback controller the loopback controller block implements the channel based diagnostic loopback function. every valid data byte belonging to a channel with diagnostic loopback enabled from the transmit hdlc processor / partial packet buffer block (thdl672) is written into a 64 word fifo. the loopback controller monitors for an idle time-slot or a time-slot carrying a channel with diagnostic loopback enabled. if either conditions hold, the current data byte is replaced by data retrieved from the loopback data fifo. 9.4 receive hdlc processor / partial packet buffer the receive hdlc processor / partial packet buffer block (rhdl672) processes up to 672 synchronous transmission hdlc data streams. each channel can be individually configured to perform flag sequence detection, bit de-stuffing and crc-ccitt or crc-32 verifi cation. the packet data is written into the partial packet buffer. at the end of a frame, packet status including crc error, octet alignment error and maximum length violation are also loaded into the partial packet buffer. alternatively, a channel can be provisioned as transparent, in which case, the hdlc data stream is passed to the partial packet buffer processor verbatim. there is a natural precedence in the alarms detectable on a receive packet. once a packet exceeds the programmable maximum packet length, no further processing is performed on it. thus, octet alignment detection, fcs verification and abort recognition are squelched on packets with a maximum length violation. an abort indication squelches octet alignment detection, minimum packet length violations, and fcs verification. in addition, fcs verification is only performed on packets that do not have octet alignment errors, in order to allow the rhdl672 to perform crc calcul ations on a byte-basis. the partial packet buffer is an 32 kbyte ram that is divided into 16-byte blocks. each block has an associated pointer which points to another block. a logical fifo is created for each provisioned channel by programming the block pointers to form a circular linked list. a channel fifo can be assigned a minimum of 3 blocks (48 bytes) and a maximum of 2048 bl ocks (32 kbytes). the depth of the channel fifos are monitored in a round-robin fashion. requests are made to the receive dma controller block (rmac672) to transfer, to the pci host memory, data in channel fifos with depths exceeding their associated threshold.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 44 9.4.1 hdlc processor the hdlc processor is a time-slice state machine which can process up to 672 independent channels. the state vector and provisioning information for each channel is stored in a ram. whenever new channel data arrives, the appropriate state vector is read from the ram, processed and written back to the ram. the hdlc state-machine can be configured to perform flag delineation, bit de-stuffing, crc verifica tion and length monitoring. the resulting hdlc data and status information is passed to the partial packet buffer processor to be stored in the appropriate channel fifo buffer. the configuration of the hdlc processor is accessed using indirect channel read and write operations. when an indirect operation is performed, the information is accessed from ram during a null clock cycle generated by the upstream receive channel assigner block (rcas672). writing new provisioning data to a channel resets the channel's entire state vector. 9.4.2 partial packet buffer processor the partial packet buffer processor controls the 32 kbyte partial packet ram which is divided into 16 byte blocks. a block pointer ram is used to chain the partial packet blocks into circular c hannel fifo buffers. thus, non-contiguous sections of the ram can be allocated in the partial packet buffer ram to create a channel fifo. system software is respons ible for the assignment of blocks to individual channel fifos. figure 4 shows an example of three blocks (blocks 1, 3, and 200) linked together to form a 48 byte channel fifo. the partial packet buffer processor is divided into three sections: writer, reader and roamer. the writer is a time-sliced state machine which writes the hdlc data and status information from the hdlc processor into a channel fifo in the packet buffer ram. the reader transfers channel fifo data from the packet buffer ram to the downstream receive dma controller block (rmac672). the roamer is a time-sliced st ate machine which tracks channel fifo buffer depths and signals the reader to service a part icular channel. if a buffer over-run occurs, the writer ends the current packet from the hdlc processor in the channel fifo with an over-run flag and ignores the rest of the packet.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 45 figure 4 ? partial packet buffer structure 16 bytes 16 bytes 16 bytes 16 bytes 16 bytes 16 bytes partial packet buffer ram block 2047 block 0 block 1 block 2 block 3 block 2047 block 0 block 1 block 2 block 3 block pointer ram block 200 block 200 0x03 0xc8 0x01 xx xx xx the fifo algorithm of the partial packet buffer processor is based on a programmable per-channel transfer size. instead of tracking the number of full blocks in a channel fifo, the processor tracks the number of transactions. whenever the partial packet writer fills a transfer-sized number of blocks or writes an end-of-packet flag to the channel fifo, a transaction is created. whenever the partial packet reader transmits a transfer-s ize number of blocks or an end-of-packet flag to the rmac672 block, a transaction is deleted. thus, small packets less than the transfer size will be naturally transferred to the rmac672 block without having to precisely track the num ber of full blocks in the channel fifo. the partial packet roamer performs the transaction accounting for all channel fifos. the roamer increments the transaction count when the writer signals a new transaction and sets a per-channel flag to indicate a non-zero transaction count. the roamer searches the flags in a round-robin fashion to decide for which channel fifo to request transfer by the rmac672 block. the roamer informs the partial packet reader of the channel to process. the reader transfers the data to the rmac672 until the channel transfer size is reached or an end of
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 46 packet is detected. the reader then informs the roamer that a transaction is consumed. the roamer updates its tr ansaction count and clears the non-zero transaction count flag if required. the roamer then services the next channel with its transaction flag set high. the writer and reader determine empty and full fifo conditions using flags. each block in the partial packet buffer has an associated flag. the writer sets the flag after the block is written and the reader clears the flag after the block is read. the flags are initialized (cleared) when the block pointers are written using indirect block writes. the writer declares a channel fifo overrun whenever the writer tries to store data to a block with a set flag. in order to support optional removal of the fcs from the packet data, the writer does not declare a block as filled (set the block flag nor increment the transaction count) until the first double word of the next block in channel fifo is filled. if the end of a packet resides in the first double word, the writer declares both blocks as full at the same time. when the reader finishes processing a tr ansaction, it examines the first double word of the next block for the end-of-packet flag. if the first double word of the next block contains only fcs bytes, the reader would, optionally, process next transaction (end-of-packet) and consume the bl ock, as it contains information not transferred to the rmac672 block. 9.5 receive dma controller the receive dma controller block (rmac672) is a dma controller which stores received packet data in host computer memory. the rmac672 is not directly connected to the host memory pci bus. memory accesses are serviced by a downstream pci controller block (gpic). the rmac672 and the host exchange information using receive packet descriptors (rpds). the descriptor contains the size and location of buffers in host memory and the packet status information associated with the data in each buffer. rpds are transferred from the rmac672 to the host and vice versa using descriptor reference queues. the rmac672 maintains all the pointers for the operation of the queues. the rmac672 provides two receive packet descriptor reference (rpdr) free queues to support small and large buffers. the rmac672 acquires free buffers by reading rpdrs from the free queues. after a packet is received, the rmac672 places the associated rpdr onto a rpdr ready queue. to minimize host bus accesses, the rmac672 maintains a descriptor reference table to store current dma information. this table contains separate dma information entries for up to 672 receive channels. 9.5.1 data structures for packet data, the rmac672 communicates with the host using receive packet descriptors (rpd), receive packet descriptor references (rpdr), the
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 47 receive packet descr iptor reference ready (rp drr) queue and the receive packet descriptor reference small and large buffer free (rpdrf) queues. the rmac672 copies packet data to data buffers in host memory. the rpd, rpdr, rpdrr queue, and small and large rpdrf queues are data structures which are used to transfer host memory data buffer information. all five data structures are manipulated by both the rmac672 and the host computer. the rpd holds the data buffer size, data buffer address, and packet status information. the rpdr is a pointer which is used to index into a table of rpds. the rpdrr queue and rpdrf queues allow the rmac672 and the host to pass rpdrs back and forth. these data structures are described in more detail in the following sections. receive packet descriptor the receive packet descriptors (rpds) pass buffer and packet information between the rmac672 and the host. both the rmac672 and the host read and write information in the rpds. the host writes rpd fields which describe the size and address of data buffers in host memory. the rmac672 writes rpd fields which provide number of bytes used in each data buffer, rpd link information, and the status of the received packet. rpds are stored in host memory in a receive packet descriptor table which is described in a later section. the receive packet descripto r structure is shown in figure 5. figure 5 ? receive packet descriptor reserved (6) ce next rpd pointer [14:0] status [5:0] data buffer start address [31:0] receive buffer size [15:0] 0 bit 31 bytes in buffer [15:0] reserved (16) offset[1:0] reserved (7) rcc[9:0] res (1) table 6 ? receive packet descriptor fields field description data buffer start address[31:0] the data buffer start address[31:0] bits point to the data buffer in host memory. this field is expected to be configured by the host during initialisation. the data buffer start address field is valid in all rpds.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 48 field description ce the chain end (ce) bit indicates the end of a linked list of rpds. when ce is set to logic one, the current rpd is the last rpd of a linked list of rpds. when ce is set to logic zero, the current rpd is not the last rpd of a linked list. the ce bit is valid for all rpds written by the rmac672 to the receive ready queue. when a packet requires only one rpd, the ce bit is set to logic one. the ce bit is ignored for all rpds read by the rmac672 from the receive free queues, each of which is assumed to point to only one buffer, i.e. not a chain. offset[1:0] the offset[1:0] bits indicate the byte offset of the data packet from the start of the buffer. if this value is non- zero, there will be ?dummy? (i .e. undefined) bytes at the start of the data buffer prior to the packet data proper. for a linked list of rpds, only the first rpd's offset field is valid. all other rpd offset fields of the linked list are set to 0. status [5:0] the status[5:0] bits indicate the status of the received packet. status[0] rx buffer overrun status[1] packet exceeds max. allowed size status[2] crc error status[3] packet length not an exact no. of bytes status[4] hdlc abort detected status[5] unused (set to 0) for a linked list of rpds, only the last rpd's status field is valid. all other rpd status fields of the linked list are invalid and should be ignored. when a packet requires only one rpd, the status field is valid. bytes in buffer [15:0] the bytes in buffer[15:0] bits indicate the number of bytes actually used in the current rpd's data buffer to store packet data. the count excludes the 'dummy' bytes inserted as a result of a non-zero offset field. a count greater than 32767 bytes indicates a packet that is shorter than the expected length of the fcs field. the bytes in buffer field is invalid when status[0] or status[4] is asserted .
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 49 field description next rpd pointer [14:0] the next rpd pointer[14:0] bits store a rpdr which enables the rmac672 to support linked lists of rpds. this field, which is only valid when ce is equal to logic zero, contains the rpdr to the next rpd in a linked list. the rmac672 links rpds when more than one buffer is needed to store a packet. the next rpd pointer is not valid for the last rpd in a linked list (when ce=1). when a packet requires only one rpd, the next rpd pointer field is not valid. rcc[9:0] the receive channel code (rcc[9:0]) bits are used by the rmac672 to associate a rpd with a channel. for a linked list of rpds, all the rpds? rcc[9:0] fields are valid. i.e. all contain the same channel value. receive buffer size [15:0] the receive buffer size[15:0] bits indicate the size in bytes of the current rpd's data buffer. this field is expected to be configured by the host during initialisation. the receive buffer size must be a non-zero integer multiple of sixteen and less than or equal to 32752. the receive buffer size field is valid in all rpds. the receive buffer size and data buffer start address fields are written only by the host. the rmac672 reads these fields to determine where to store packet data. all other fields are written only by the rmac672. receive packet descriptor table the receive packet descriptor table resides in host memory and stores all the rpds. the rpd table can contain a maximum of 32768 rpds. the base of the rpd table is user programmable using the rx packet descriptor table base (rpdtb) register. the table is indexed by a receive packet descriptor reference (rpdr) which is a 15-bit pointer defining the offset of a rpd from the table base. thus, as shown in the following diagram, a rpd can be located by adding the rpdr to the rx packet descriptor table base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 50 figure 6 ? receive packet descriptor table rpdtb[31:4] = rx packet descriptor table base register rpdr[14:0] = receive packet descriptor reference rpd_addr[31:0] = receive packet descriptor address rpdtb bit 0 bit 31 rpd_addr rpd 1 rpd 2 rpd 32768 dword 0 dword 1 dword 2 dword 3 rpdtb[31:4] rpdr[14:0] bit 31 bit 0 + = rpd_addr[31:0] dword 0 dword 0 0000 0000 dword 3 dword 3 the receive packet descriptor table resides in host memory. the rx packet descriptor table base register resides in the rmac672; this register is initialised by the host. the rpdrs reside in host memory and are accessed using receive packet queues which are described in the next section.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 51 receive packet queues receive packet queues are used to transfer rpdrs between the host and the rmac672. there are three queues: a rpdr large buffer free queue (rpdrlfq), a rpdr small buffer free queue (rpdrsfq) and a rpdr ready queue (rpdrrq). the free queues contain rpdrs referencing rpds that define free buffers. the ready queue contains rpdrs referencing rpds that define buffers ready for host processing. the rmac672 pulls rpdrs from the free queues when it needs free data buffers. the rmac672 places an rpdr onto the ready queue after it has filled the buffers with data from each complete packet. the host removes rpdrs from the ready queue to process the data buffers. the host places the rpdrs back onto the free queues after it finishes reading the data from the buffers. when starting to process a packet, the rmac672 uses a small buffer rpd to store the first buffer of packet data. if the packet data requires more than one buffer, the rmac672 uses large buffer rpds to store the remainder of the packet. the rmac672 links together all the rpds required to store the packet and returns the rpdr associated with the first rpd onto the ready queue. all receive packet queues reside in host memory and are defined by the rx queue base (rqb) register and index registers which reside in the rmac672. the rx queue base is the base address for the receive packet queues. each packet queue has four index registers which define the start and end of the queue and the read and write locations of the queue. each index register is 16 bits in length and defines an offset from the rx queue base. thus, as shown in the figure 7, the host address of a rpdr is calculated by adding the index register to the rx queue base register. the host initializes the rx queue base register and all the index registers. when an entity (either the rmac672 or the host) removes elements from a queue, the entity updates the read pointer for that queue. when an entity (either the rmac672 or the host) places elements onto a queue, the entity updates the write pointer for that queue. the read index for each queue points to the last valid rpdr read while the write index points to where the next rpdr can be written. the start index points to the first valid location within the queue; an rpdr can be written to this location. however, the end index points to a location that is beyond a queue; an rpdr can not be written to this location. note however, the start index of one queue can be set to the end index of another queue. a queue is empty when the read index is one less than the write index; a queue is also empty if the read index is one less than the end index and the write index equals the start index. a queue is full when the read index is equal to the write index. figure 7 shows the rpdr reference queues.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 52 figure 7 ? rpdrf and rpdrr queues rqb[31:2] = rx queue base register rpdrrqs[15:0] = rpdr ready queue start register rpdrrqw[15:0] = rpdr ready queue write register rpdrrqr[15:0] = rpdr ready queue read register rpdrrqe[15:0] = rpdr ready queue end register receive packet descriptor (rpd) reference queues base address: index registers: ready queue: rpdrsfqs[15:0] = rpdr small free queue start register rpdrsfqw [15:0] = rpdr small free queue w rite register rpdrsfqr[15:0] = rpdr small free queue read register rpdrsfqe[15:0] = rpdr small free queue end register large buffer free queue: small buffer free queue: rpdrlfqs[15:0] = rpdr large free queue start register rpdrlfqw [15:0] = rpdr large free queue w rite register rpdrlfqr[15:0] = rpdr large free queue read register rpdrlfqe[15:0] = rpdr large free queue end register base address + index register ------------------------- host address 00 rqb[31:2] index[15:0] + ad[31:0] rx packet descriptor reference queue memory map rqb bit 0 bit 31 rpdr valid rpdr 256kb rpd reference queues host memory rpdrrqs rpdrrqw rpdrrqr rpdrrqe rpdrlfqs rpdrlfqw rpdrlfqr rpdrlfqe rpdrsfqs rpdrsfqw rpdrsfqr rpdrsfqe rpdr rpdr rpdr rpdr rpdr rpdr rpdr rpdr rpdr rpdr rpdr 00 status + rpdr status + rpdr status + rpdr status + rpdr status + rpdr status + rpdr
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 53 note that the maximum value to which an end pointer may be set is ffff hex, resulting in a maximum offset from the queue base address of (4*(ffff-1)) = 3fff8 hex. an end pointer must not be set to 0 hex in an attempt to include offset 3fffc hex in a queue. as shown in figure 7, the ready queue elements have a status field as well as an rpdr field. the rmac672 fills in the stat us field to mark whether a packet was successfully received or not. the host reads the status field. the ready queue element is shown in table 7 below along with the definition of the status bits. if the rmac672 requires a buffer of a particular size (i.e. small or large) and no rpdr is available in the corresponding free queue, a rpdr from the other free queue is substituted. the host may, therefore, force the rmac672 to store received data in buffers of only one size by setting one of the free queues to zero length, i.e. by setting the start and end index registers of one of the queues to equal values. if the rmac672 requires a buffer and neither free queue contains rpdrs, an rpq_erri interrupt is generated. table 7 ? rpdrr queue element bit 16 bit 0 status[1:0] rpdr[14:0] field description status[1:0] the encoding for the status field is as follows: 00 ? successful reception of packet. 01 ? unsuccessful reception of packet. 10 ? unprovisioned partial packet. 11 ? partial packet returned due to rawmax limit being reached. rpdr[14:0] the rpdr[14:0] field defines the offset of the first rpd in a linked chain of rpds, each pointing to a buffer containing the received data. as described previously, the rmac672 links rpds together if more than one buffer is needed for a packet. the rmac672 links additional buffer rpds to the end of the chain as required until the entire packet is copied to host memory (provided that the host has not disabled use of both the small and large free queues by setting one of them to length zero). after storing the packet data, the rmac672 places the status+rpdr for the first rpd onto the ready queue. only the rpdr associated with the first rpd is placed onto the ready queue. all other required rpds are linked to the first rpd as shown in figure 8.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 54 although a status+rpdr only totals to 17 bits, each queue entry is a dword, i.e. 32 bits. when the rmac672 block writes a status+rpdr to the ready queue, it sets the remaining 7 bits in the third byte to zero and the fourth byte is unmodified. figure 8 ? rpdrr queue operation rx packet descriptor reference ready queue bit 0 bit 31 rpdrrq_start_addr rpdrrq_end_addr rpdrrq_read_addr rpdrrq_write_addr rpd - 16 bytes rpd - 16 bytes rpd - 16 bytes rpd - 16 bytes rpd - 16 bytes buffer -packet m buffer -packet n buffer -start of packet o buffer -middle of packet o buffer -end of packet o status+rpdr status+rpdr status+rpdr receive channel descriptor reference table on a per-channel basis, the rmac672 caches information such as the current dma information in a receive channel descriptor reference (rcdr) table. the rmac672 can process 672 channels and stores three dwords of information per channel. this information is cached internally in order to
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 55 decrease the number of host bus accesses required to process each data packet. the structure of the rcdr table is shown in figure 9. figure 9 ? receive channel descriptor reference table rpd pointer[14:0] bytes avail. in buffer[14:0] start rpd pointer[14:0] dma current address[31:0] rbc[1:0] bit 0 bit 31 rcc 0 rcc 1 rcc 671 rpd pointer[14:0] start rpd pointer[14:0] dma current address[31:0] rpd pointer[14:0] start rpd pointer[14:0] dma current address[31:0] buffer size[14:0] buffer size[14:0] buffer size[14:0] v v v bytes avail. in buffer[14:0] rbc[1:0] bytes avail. in buffer[14:0] rbc[1:0] res res res table 8 ? receive channel descriptor reference table fields field description bytes available in buffer[15:0] this field is used to keep track of the number of bytes available in the current data buffer. the rmac672 initialises the bytes available in buffer to the receive buffer size minus the offset at the head of the buffer. the field is decremented each time a byte is written into the buffer. rbc[1:0] this field is used to keep track of the number of buffers used when storing ?raw? (i.e. non packet delimited) data. the rmac672 initialises the rbc field to the value of the rawmax[1:0] field in the rmac control register. the field is decremented each time a buffer is filled with data. if the field reaches zero, the chain of rpds is placed on the ready queue and a new chain started. rpd pointer[14:0] this field contains the pointer to the current rpd.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 56 field description buffer size[14:0] this field contains the size in bytes of the buffer currently being written to. v this bit (valid) indicates whether a packet is currently being received on the dma channel. when the v bit is set to 1, the other fields in the rcdr table entry for the dma channel contain valid information. start rpd pointer[14:0] this field contains the pointer to the first rpd for the packet being received. dma current address[31:0] the dma current address [31:0] bits holds the host address of the next dword in the current buffer. the rmac672 increments this field on each access to the buffer. 9.5.2 dma transaction controller the dma transaction controller coordinates the reception of data packets from the receive packet interface and their subsequent storage in host memory. a packet may be received over a number of separate transactions, interleaved with transactions belonging to other dma channel s. as well as sending the received data to host memory, the dma transaction controller initiates data transactions of its own for the purposes of maintaining the data structures (queues, descriptors, etc.) in host memory. 9.5.3 write data pipeline/mux the write data pipeline/mux performs two functions. first, it pipelines receive data between the rhdl672 block and the gpic block, inserting enough delay to enable the dma transaction controller to generate appropriate control signals at the gpic interface. second, it provides a multiplexor to the data out lines on the gpic interface, allowing the dma transaction controller to output data relating to the transactions the controller itself initiates. 9.5.4 descriptor information cache the descriptor information cache provides the storage for the receive channel descriptor reference (rcdr) t able described abov e (figure 9).
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 57 9.5.5 free queue cache the free queue cache block implements the 6 element rpdr small buffer free queue cache and the 6 element rpdr large buffer free queue cache. these caches are used to store free small buffer and large buffer rpdrs. caching rpdrs reduces the number of host bus accesses that the rmac672 makes. each cache is managed independently. the elements of the cache are consumed one at a time as they are needed by the rmac672. the rpdr small buffer cache is reloaded when it is empty and the rmac672 requires a new small buffer rpdr. the large buffer rpdr cache is reloaded when it is empty and the rmac672 requires a new large buffer rpdr. when reloading either of the caches, the appropriate cache contro ller will read up to six new elements. the cache controller may read fewer than six elements if there are fewer than six new elements available, or the read pointer index is within six elements of the end of the free queue. if the read pointer is near the end of the free queue, the cache controller reads only to the end of the queue and does not start reading from the top of the queue until the next time a reload is required. to do so would require two host memory transactions and would be of no benefit. 9.6 pci controller the general-purpose peripheral component interconnect controller block (gpic) provides a 32-bit master and target interface core which contains all the required control functions for full peripheral component interconnect (pci) bus revision 2.1 compliance. communications between the pci bus and other freedm-32p672 blocks can be made th rough either an internal asynchronous16-bit bus or through one of two synchronous fifo interfaces. one of the fifo interfaces is dedicated to servicing the receive dma controller block (rmac672) and the other to the transmit dma controller block (tmac672). the gpic supports a 32-bit pci bus operating at up to 66 mhz and bridges between the timing domain of the dma controllers (sysclk) and the timing domain of the pci bus (pciclk). the gpic is backwards compatible and will operate at 33 mhz when connected to a 33 mhz pci bus. by itself, the gpic does not generate any pci bus accesses. all transactions on the bus are initiated by another pci bus master or by the core device. the gpic transforms each access to and from the pci bus to the intended target or initiator in the core device. except for the configuration space registers and parity generating/checking, the gpic performs no operations on the data. the gpic is made up of four sections: master state machine, a target state machine, internal microprocessor bus interface and error/bus controller. the
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 58 target and master blocks operate independent of each other. the error/bus control block monitors the control signal s from the target and master blocks to determine the state of the pci i/o pads. this block also generates and/or checks parity for all data going to or co ming from the pci bus. the internal microprocessor bus interface block contains configuration and status registers together with the production test logic for the gpic block. 9.6.1 master machine the gpic master machine translates requests from the rmac672 and tmac672 block interfaces into pci bus transactions. the gpic initiates four types of pci cycles: memory read (burst or single), memory read multiple, memory read line and memory write (burst or single). the number of data transfers in any cycle is controlled by the dma controllers. the maximum burst size is determined by the particular data path. a read cycle to the rmac672 is restricted to a maximum burst size of 8 dwords and a write cycle is limited to a maximum of 64. the tmac672 interface has a limit of 64 dwords on a read cycle and 8 on a write cycle. in response to a dma controller requesting a cycle, the gpic must arbitrate for control of the pci bus. in the event that the rmac672 and tmac672 request service simultaneously, the gpic66 processes the rmac672 dma operation first. when an external pci bus arbitrator issues a grant in response to the request from the gpic, the master state machine monitors the pci bus to insure that the previous master has completed its tr ansaction and has released the bus before beginning the cycle. once the gpic has control of the bus, it will assert the frame signal and drive the bus with the address and command. the value for the address is provided by the selected dma controller. after the initial data transfer, the gpic tracks the address for all remaining transfers in the burst internally in case the gpic is disconnected by the target and must retry the transaction. the target of the gpic master burst cycle has the option of stopping or disconnecting the burst at any point. in the event of a target disconnect the gpic will terminate the present cycle and release the pci bus. if the gpic is asserting the request line at the time of the disconnect, it will remove the request for two pci clock cycles then reassert it. when the pci bus arbitrator returns the grant, the gpic will rest art the burst access at the next address and continue until the burst is completed or repeat the sequence if the target disconnects again. during burst reads, the gpic accepts the data without inserting any wait states. data is written directly into the read fifo where the rmac672 or tmac672 can
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 59 remove it at its own rate. during burst writes, the gpic will output the data without inserting any wait states, but may terminate the transaction early if the local master fails to fill the write fifo with data before the gpic requires it. (if a write transaction is term inated early due to data st arvation, the gpic will automatically initiate a further transaction to write the remaining data when it becomes available.) normally, the gpic will begin requesting the pci bus for a write transaction shortly after data starts to be loaded into the write fifo by the rmac672 or tmac672. the rmac672, however, is not required to supply a transaction length when writing packet data and in addition, may insert pauses during the transfer. in the case of packet data writes by the rmac672, the gpic will hold off requesting the pci bus until the write fifo has filled up with a number of dwords equal to a programmable threshold. if the fifo empties without reaching the end of the trans ition, the gpic will termi nate the current transaction and restart a new transaction to transfer any remaining data when the rmac672 signals an end of transaction. beginning the pci transaction before all the data is in the write fifo allows the gpic to reduce the impact of the bus latency on the core device. each master pci cycle generated by the gpic can be terminated in three ways: completion, timeout or master abort. the normal mode of operation of the gpic is to terminate after transferring all the data from the master fifo selected. as noted above this may involve multiple pci accesses because of the inability of the target to accept the full burst or data starvation during writes. after the completion of the burst transfer the gp ic will release the bus unless another fifo is requesting service, in which case if the grant is asserted the gpic will insert one idle cycle on the bus and then start a new transfer. the maximum duration of the a master burst cycle is controlled by the value set in the latency timer register in the gpic configuration register block. this value is set by the host on boot and is loaded into a counter in the gpic master state at the start of each access. if the counter reaches zero and the grant signal has been removed the gpic will rel ease the bus regardless of whether it has completed the present burst cycle. this type of termination is referred to as a master time-out. in the case of a master time-out the gpic will remove the request signal for two pci clocks and then reassert it to complete the burst cycle. if no target responds to the address placed on the bus by the gpic after 4 pci clocks the gpic will terminate the cycle and flag the cycle in the pci command/ status configuration register as a master abort. if the stop on error enable (soe_e) bit is set in the gpic command register, the gpic will not process any more requests until the error condition is cleared. if the soe_e is not set, the gpic will discard the request and indicate to the local master that the cycle is
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 60 complete. this action will result in any write data being lost and any read data being erroneous. 9.6.2 master local bus interface the master local bus is a 32 bit data bus which connects the local master device to the gpic. the gpic contains two local master interface blocks, with one supporting the rmac672 and the other the tmac672. each local master interface has been optimised to support the traffic pattern generated by the rmac672 or the tmac672 and are not interchangeable. the data path between the gpic and local master device provides a mechanism to segregate the system timing domain of the core from the pci bus. transfers on each of the rmac672 and tmac672 interfaces are timed to its own system clock. the dma controllers isolated from all aspects of the pci bus protocol, and instead ?sees? a simple synchronous protocol. read or write cycles on the local master bus will initiate a request for se rvice to the gpic which will then transfer the data via the pci bus. the gpic maximises data throughput between the pci bus and the local device by paralleling local bus data transfers with pci access latency. the gpic allows either dma controller to write data independent of each other and independent of pci bus control. the gpic temporarily buffers the data from each dma controller while it is arbitrating for control of the pci bus. after completion of a write transfer, the dma controller is then released to perform other tasks. the gpic can buffer only a single transaction from each dma controller. read accesses on the local bus are optimised by allowing the dma controllers access to the data from the pci bus as s oon as the first data becomes available. after the initial synchronisation and pci bus latency data is transferred at the slower of pci bus rate or the core logic sysclk rate. once a read transaction is started, the dma controller is held waiting for the ready signal while the gpic is arbitrating for the pci bus. all data is passed between the gpic and the dma controllers in little endian format and, in the default mode of operation, the gpic expects all data on the pci bus to also be in little endian format. the gpic provides a selection bit in the internal control register which allows the endian format of the pci bus data to be changed. if enabled, the gpic will swizzle all packet data on the pci bus (but not descriptor references and the contents of descriptors). the swizzling is performed according to the ?byte address invariance? rule, i.e. the only change to the data is the mirror-imaging of byte lanes. the interface for the rmac672 provides for byte addressability of write transactions whereas the interface for the tmac672 provides for byte
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 61 addressability of read transac tions. other tr ansactions must be dword aligned. for byte-addressable transactions, the data transferred between the local device and the gpic need not be dword aligned with the data as it is presented on the pci bus. the gpic will perform any byte-realignment required. in order to complete a transfer involving byte re-alignment, the gpic may need to add an extra burst cycle to the pci transaction. 9.6.3 target machine the gpic target machine performs all the required functions of a stand alone pci target device. the target block performs three main functions. the first is the target state machine which controls the protocol of pci target accesses to the gpic. the second function is to provide all pci configuration registers. last, the target block provides a target interface to the cbi registers in the other freedm-32p672 blocks. the gpic tracks the pci bus and dec odes all addresses and commands placed on the bus to determine whether to respond to the access. the gpic responds to the following types of pci bus commands only: configuration read and write, memory read and write, memory-read-multiple and memory-read-line which are aliased to memory read and memory-write-and-invalidate which is aliased to memory write. the gpic will ignore any access that falls within the address range but has any other command type. after accepting a target access as a medium speed device, the freedm- 32p672 inserts one wait state for a configuration read/write and five wait states for other command types before completing the transaction by asserting trdyb. burst accesses to the gpic are accepted provided they are of linear type. if a master makes a memory access to the gpic with the lower two address bits set to any value but "00" (linear burst type) the gpic ignores the cycle. burst accesses of any length are accepted, but the freedm-32p672 will disconnect if the master inserts any wait states during the transaction. the freedm-32p672 will also disconnect on every read and write access to configuration space after transferring one dword of data. figure 10 illustrates the gpic address space.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 62 figure 10 ? gpic address map cbi registers base address cbi registers 8kb pci address map 0b 4gb the gpic responds with medium timing to master accesses. (i.e. devselb is asserted 2 pciclk cycles after frameb asserted). the gpic inserts five wait states on reads to the internal cbi register space (six wait states for the 2nd and subsequent dwords of a bur st read). the target machine will only terminate an access with a retry if the target is locked and another master tries to access the gpic. the gpic will terminate any access to a non-burst area with a disconnect and always with data transferred. the target does not support delayed transactions. the gpic will perform a target-abort termination only in the case of an address parity error in an address that the gpic claims.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 63 9.6.4 cbi bus interface the cbi bus interface provides access to the cbi address space of the freedm-32p672 blocks. the cb i address space is set by the associated bar in the pci configuration registers. write transfers to the cbi space always write all 32 bits provided that at least one byte enable is asserted. a write command with all byte enables negated will be ignored. read transfers always return the 32 bits regardless of the status of the byte enables, as long as at least one byte enable is asserted. a read command with all byte enables negated will be ignored. 9.6.5 error / bus control the error/bus control block monitors signals from both the target block and master block to determine the direction of the pci bus pads and to generate or check parity. after reset, the gpic sets all bi-directional pci bus pads to inputs and monitors the bus for accesses. the error/bus control unit remains in this state unless either the master requests the pci bus or the target responds to a pci master access. the error/bus control unit decodes the state of each state machine to determine the direction of each pci bus signal. all pci bus devices are required to check and generate even parity across ad[31:0] and c/beb[3:0] signals. the gpic generates parity on master address and write data phases; the target generates parity on read data phases. the gpic is required to check parity on all pci bus phases even if it is not participating in the cycle. but, the gpic will report parity errors only if the gpic is involved in the pci cycle or if the gpic detects an address parity error or data parity is detected in a pci special cycle. the gpic updates the pci configuration status register for all detected error conditions. 9.7 transmit dma controller the transmit dma controller block (tmac672) is a dma controller which retrieves packet data from host computer memory for transmission. the minimum packet data length is two bytes. the tmac672 communicates with the host computer bus through the master interface connected to pci controller block (gpic) which translates host bus specific signals from the host to the master interface format. the tmac672 uses the master interface whenever it wishes to initiate a host bus read or write; in this case, the tmac672 is the initiator and the host memory is the target. the tmac672 and the host exchange information using transmit descriptors (tds). the descriptor contains the size and location of buffers in host memory
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 64 and the packet status information associated with the data in each buffer. tds are transferred from the tmac672 to the host and vice versa using descriptor reference queues. the tmac672 maintains all the pointers for the operation of the queues. the tmac672 acquires buffers with data ready for transmission by reading tdrs from a tdr ready queue. after a packet has been transmitted, the tmac672 places the associated tdr onto a tdr free queue. to minimise host bus accesses, the tmac672 maintains a descriptor reference table to store current dma information. this table contains separate dma information entries for up to 672 transmit channels. the tmac672 also performs per-channel sorting of packets received in the tdr ready queue to eliminate head-of-line blocking. 9.7.1 data structures the tmac672 communicates with the host using transmit descriptors (td), transmit descriptor references (tdr), the transmit data reference ready (tdrr) queue and the transmit data reference free (tdrf) queue. the tmac672 reads packet data from data buffers in host memory. the td, tdr, tdrr queue, and tdrf queue are dat a structures which are used to transfer host memory data buffer information. all four data structures are manipulated by both the tmac672 and the host computer. the td holds the data buffer size, data buffer address, and other packet information. the tdr is a pointer which is used to index into a table of tds. the tdrr queue and tdrf queue allow the tmac672 and the host to pass tdrs back and forth. these data structures are described in more detail in the following sections. transmit descriptor the transmit descriptors (tds) pass buffer and packet information between the tmac672 and the host. both the tmac672 and the host read and write information in the tds. tds are stored in host memory in a transmit descriptor table. the transmit descriptor structure is shown in figure 11. figure 11 ? transmit descriptor bit 31 0 data buffer start address [31:0] bytes in buffer [15:0] p vm ce tmac next td pointer[14:0] ioc abt host next td pointer[14:0] transmit buffer size[15:0] res (2) reserved (16) tcc[9:0]
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 65 table 9 ? transmit descriptor fields field description data buffer start address [31:0] the data buffer start address[31:0] bits point to the data buffer in host memory. the data buffer start address field is valid in all tds bytes in buffer [15:0] the bytes in buffer[15:0] field is used by the host to indicate the total number of bytes to be transmitted in the current td. zero length buffers are illegal. p the priority bit is set by the host to indicate the priority of the associated packet in a two level quality of service scheme. packets with its p bit set high are queued in the high priority queue in the tmac672. packets with the p bit set low are queued in the low priority queue. packets in the low priority queue will not begin transmission until the high priority queue is empty. abt the abort (abt) bit is used by the host to abort the transmission of a packet. when abt is set to logic 1, the packet will be aborted after all the data in the buffer has been transmitted. if abt is set to logic 1 in the current td, the m bit must be set low and the ce bit must be set to high. ioc the interrupt on complete (ioc) bit is used by the host to instruct the tmac672 to interrupt the host when the current td's data buffer has been read. when ioc is logic 1, the tmac672 asserts the ioci interrupt when the data buffer has been read. additionally, the free queue fifo will be flushed. if ioc is logic zero, the tmac672 will not generate an interrupt and the free queue fifo will operate normally.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 66 field description ce the chain end (ce) bit is used by the host to indicate the end of a linked list of tds presented to the tmac672. the linked list can contain one or more packets as delineated by the m bit (see above). when ce is set to logic 1, the current td is the last td of a linked list of tds. when ce is set to logic 0, the current td is not the last td of a linked list. when the current td is not the last of the linked list, the host next td pointer[14:0] field is valid, otherwise the field is not valid. note: when ce is set to logic 1, the only valid value for m is logic 0. note: when presenting raw (i.e. unpacketised) data for transmission, the host should code the m and ce bits as for a single packet chain, i.e. m=1, ce=0 for all tds except the last in the chain and m=0, ce=1 for the last td in the chain. tcc[9:0] the transmit channel code (tcc[9:0]) bits are used by the host to associate a channel with a td pointed to by a tdr. all tcc[9:0] fields in a linked list of tds must be set to the same value. v the v bit is used to indicate that the tmac next td pointer field is valid. when set to logic 1, the tmac next td pointer[14:0] field is valid. when v is set to logic 0, the tmac next td pointer[14:0] field is invalid. the v bit is used by the host to reclaim data buffers in the event that data presented to the tmac672 is returned to the host due to a channel becoming unprovisioned. the v bit is expected to be initialised to logic 0 by the host.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 67 field description tmac next td pointer [14:0] the tmac next td pointer[14:0] bits are used to store tdrs which permits the tmac672 to create linked lists of tds passed to it via the tdrr queue. the tds are linked with other tds belonging to the same channel and same priority level. in the case that data presented to the tmac672 is returned to the host due to a channel becoming unprovisioned, a tdr pointing to the start of the per-channel linked list of tds is placed on the tdrf queue. it is the responsibility of the host to follow the tmac672 and host links in order to recover all the buffers. m the more (m) bit is used by the host to support packets that require multiple tds. if m is set to logic 1, the current td is just one of several tds for the current packet. if m is set to logic 0, this td either describes the entire packet (in the single td packet case) or describes the end of a packet (in the multiple td packet case). note: when m is set to logic 1, the only valid value for ce is logic 0. host next td pointer [14:0] the host next td pointer[14:0] bits are used to store tdrs which permits the host to support linked lists of tds. as described above, linked lists of tds are terminated by setting the ce bit to logic 1. linked lists of tds are used by the host to pass multiple td packets or multiple packets associated with the same channel and priority level to the tmac672. transmit buffer size [15:0] the transmit buffer size[15:0] field is used to indicate the size in bytes of the current td's data buffer. (n.b. the tmac672 does not make use of this field.) transmit descriptor table the transmit descriptor table, which resides in host memory, contains all of the transmit descriptors referenced by the tmac672. to access a td, the tmac672 takes a tdr from a tdrr queue or from the tcdr table and adds 16 times its value (because each td is 16 bytes in size) to the transmit descriptor table base (tdtb) pointer to form the actual address of the td in host memory. each td must reside in the transmit descriptor table. the
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 68 transmit descriptor table can contain a maximum of 32768 tds. the base of the transmit descriptor table is user programmable using the tmac tx descriptor table base register. thus, as shown below, each td can be located using a transmit descriptor reference (tdr) combined with the tmac tx descriptor table base register. figure 12 ? transmit descriptor table tdtb[31:4] = tx descriptor table base register tdr[14:0] = transmit descriptor reference td_addr[31:0] = transmit descriptor address tdtb bit 0 bit 31 td_addr td1 td2 td 32768 dword 0 dword 1 dword 2 dword 3 tdtb[31:4] tdr[14:0] bit 31 bit 0 + = td_addr[31:0] dword 0 dword 0 0000 0000 dword 3 dword 3
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 69 transmit queues pointers to the transmit descriptors (tds) containing packet(s) ready for transmission are passed from the host to the tmac672 using the transmit descriptor reference ready (tdrr) queue, which resides in host memory. pointers to transmit descriptor structures whose buffers have been read by the tmac672 are passed from the tmac672 to the host using the transmit descriptor reference free (tdrf) queue, which also resides in host memory. the tmac672 contains a free queue cache which can store up to six tdrs. if caching is enabled, free tdrs are written into the tdrf queue six at a time, to reduce the number of host memory accesses. the free queue cache is flushed to the tdrf queue if the interrupt on completion (ioc) bit is set in the td, which sends the corresponding tdr directly to the tdrf queue. the free queue cache is also flushed to the tdrf queue if the fqflush register bit is set high. the fqflush register bit is self clearing. the queues, shown in figure 13 are defined by a common base pointer residing in the transmit queue base register and eight offset pointers, four per queue. for each queue, two pointers define the start and the end of the queue, and two pointers keep track of the current read and write locations within the queue. the read pointer for each queue points to the offset of the last valid tdr read, and the write pointer points to the offset where next tdr can be written. the end of a queue is not a valid location for a tdr to be read or written. a queue is empty when the read pointer is one less than the write pointer or if the read pointer is one less than the end pointer and the write pointer equals the start pointer. a queue is full when the read pointer is equal to the write pointer. each queue element is 32 bits in size, but only the least significant 18 bits are valid. the 18 least significant bits consist of a 15-bit tdr and three status bits for the td pointed at by this tdr. the status bits are used by the tmac672 to inform the host of the success or failure of transmission (see table 10). when the tmac672 writes tdrs to the tdrf queue, it sets bits [23:18] of the queue element to 0 and leaves bits [31:24] unaltered. once a tdr is placed on the tdrf queue, the freedm-32p672 will make no further accesses to the td nor the associated buffer. note that the maximum value to which an end pointer may be set is ffff hex, resulting in a maximum offset from the queue base address of (4*(ffff-1)) = 3fff8 hex. an end pointer must not be set to 0 hex in an attempt to include offset 3fffc hex in a queue.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 70 figure 13 ? tdrr and tdrf queues transmit descriptor referance queues tqb[31:2] = tx queue base register tdrfqs[15:0] = tdr free queue start register tdrfqw[15:0] = tdr free queue write register tdrfqr[15:0] = tdr free queue read register tdrfqe[15:0] = tdr free queue end register base address: index registers: free: ready: tdrrqs[15:0] = tdr read y queue start re g iste r tdrrqw[15:0] = tdr read y queue write re g iste r tdrrqr[15:0] = tdr ready queue read register tdrrqe[15:0] = tdr read y queue end re g iste r base address + index register ------------------------- pci address 00 tqb[31:2] index[15:0] + a d[31:0] tx descriptor reference queue memory map tqb tdrrqw bit 0 bit 31 tdrfqs tdrfqe tdrfqr tdrfqw status + tdr tdrrqs tdrrqe tdrrqr valid tdr status + tdr status + tdr status + tdr status + tdr 256kb tdr reference queues pci host memory 00 tdr tdr tdr tdr tdr tdr status + tdr
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 71 table 10 ? transmit descriptor reference bit 17 bit 0 status[2:0] tdr[14:0] field description status[2:0] the tmac672 fills in the status field to indicate to the host the results of processing the td. the encoding is: status[1:0] description 00 last or only buffer of packet, buffer read. 01 buffer of partial packet, buffer read. 10 unprovisioned channel, buffer not read. 11 malformed packet (e.g. bytes in buffer field set to 0), buffer not read. status[2] description 0 no underflow detected. 1 underflow detected. tdr[14:0] the tdr[14:0] field contains the offset of the td returned. if a tdr is returned to the host with the status field set to ?10? (unprovisioned channel), the tdr may point to a binary tree of tds and buffers (as indicated by the ce and v bits in the tds). it is the responsibility of the host to traverse the tree to reclaim all the buffers. if a tdr is returned to the host with the status field set to any other value, the t dr will only point to one td and buffer regardless of the values of v and ce in that td. the underflow status bit (status[2]) is normally attached to the tdr belonging to a packet experiencing underflow. for long packets spanning multiple buffers, underflow is reported only once at the first available tdr of that channel. all subsequent tdrs of that packet will be returned normally without the underflow status. in rare cases, due to internal buffering by the freedm-32p672, a packet may experience underflow at the very end of a packet, just as the tdr is being returned to the tdr free queue. the underflow status will then be reported in the first tdr of the immediate next packet of that channel. because of the uncertainty with the reporting of underflows between the current verse the subsequent packet, the underflow status should only be used to gather performance statistics on channels and not for initiating packet specific responses such as retransmission.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 72 transmit channel descriptor reference table the tmac672 maintains a transmit c hannel descriptor reference (tcdr) table in which is stored certain information relating to dma activity on each channel together with td pointers which are used by the tmac672 to sort packet chains supplied by the host into per-channel linked lists (see below). the caching of dma-related information reduces the number of host bus accesses required to process each data packet, while the sorting into per-channel linked lists eliminates head of line blocking. each channel is provided with two entries in the tcdr table, one for high priority packets (pri 1) and one for low priority packets (pri 0). the structure of the tcdr table is shown in figure 14 below. figure 14 ? transmit channel descriptor reference table current td pointer [14:0] last td pointer [14:0] host td pointer [14:0] dma current address[31:0] bit 0 bit 33 tcc 0, pri 0 tcc 671, pri 1 bytes to tx [15:0] reserved (12) res next td pointer [14:0] d a mce ioc abrt pip na u res v tcc 1, pri 0 current td pointer [14:0] last td pointer [14:0] host td pointer [14:0] dma current address[31:0] bytes to tx [15:0] reserved (12) res next td pointer [14:0] d a mce ioc abrt pip na v current td pointer [14:0] last td pointer [14:0] host td pointer [14:0] dma current address[31:0] bytes to tx [15:0] reserved (12) res next td pointer [14:0] d a mce ioc abrt pip na v u res u res res res res res res res
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 73 table 11 ? transmit channel descriptor reference table fields field description na indicates that a ?null abort? is to be sent to the downstream block when it next requests data on this channel. the na bit is set if a mal-formed td is encountered while searching down a host chain. abrt a copy of the abrt bit in the td currently being read. ioc a copy of the ioc bit in the td currently being read. m a copy of the m bit in the td currently being read. ce a copy of the ce bit in the td currently being read. a indicates if this channel is active (i.e. provisioned). if the channel is active, the a bit is set to logic 1. if the channel is inactive, the a bit is set to logic 0. d indicates whether the linked list of packets for this channel is empty or not. if the d bit is set to logic 1, the list is not empty and the current td pointer field is valid (i.e., it points to a valid td). if the d bit is set to logic 0, the list is empty and the current td pointer field is invalid. current td pointer [14:0] offset to the td currently being read. (see figure 15) bytes to tx[15:0] the bytes to tx[15:0] bits are used to indicate the total number of bytes that remain to be read in the current buffer. each access to the data buffer decrements this value. a value of zero in this field indicates the buffer has been completely read. host td pointer [14:0] a copy of the host next td pointer field of the td currently being read, i.e. a pointer to the next td in the chain currently being read. (see figure 15) dma current address[31:0] the dma current address [31:0] bits hold the address of the next dword in the current buffer. this field is incremented on each access to the buffer. u indicates that an underflow has occurred on this channel. this bit is set in response to an underflow indication for the downstream thdl672 block and is cleared when a tdr is written to the tdr free queue (or to the free queue cache).
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 74 field description pip the packet transfer in progress bit indicates that a packet is currently being transmitted on this channel at this priority level. last td pointer [14:0] offset to the head of the last host-linked chain of tds to be read. (see figure 15) v indicates if the linked list of packets for this channel contains more than one host-linked chain (see figure 15). if the v bit is set to logic 1, the list contains more than one chain and the next and last td pointer fields are valid. if the v bit is set to logic 0, the list is either empty or contains only one host-linked chain and the next and last td pointer fields are invalid. next td pointer [14:0] offset to the head of the next host-linked chain of tds to be read. (see figure 15) transmit descriptor linking as described above, the tcdr table cont ains pointers whic h the tmac672 uses to construct linked lists of data packets to be transmitted. after the host places a new tdr in the tdr ready queue, the tmac672 retrieves the tdr and links it to the td pointed at by the last td pointer field. the tmac672 may create up to 1,344 linked lists, viz. a high-priority list and a low-priority list for each dma channel. whenever a new data packet is requested by the downstream block, the tmac672 picks a packet from the high-prior ity linked list unless it is empty, in which case, a packet from the low-priority linked list is used.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 75 figure 15 ? td linking last tdr p1 td data td td td td data p1 data p1 data p2 data data p3 p3 p4 next tdr td td tcdr table tmac link tmac link host link host link host link host link curr. tdr host tdr v=1 m=1 ce=0 v=0 m=0 ce=1 v=1 m=1 ce=0 m=1 ce=0 m=0 ce=1 m=0 ce=0 m=0 ce=1 the host links the tds vertically while the tmac672 links tds horizontally. figure 15 shows the tds for packets p1 and p2 linked by the host before the tdr is placed on the tdrr queue, as are the tds for packet p3 and p4. packet p3 is linked to packet p1 by the tmac672, as is packet p4 linked to
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 76 packet p3. the tmac672 indicates valid horizontal links by setting the v bit to logic 1. 9.7.2 task priorities the tmac672 must perform a number of tasks concurrently in order to maintain a steady flow of data through the system. the main tasks of the tmac672 are managing the ready queue (i.e. removing chains of data packets from the queue and attaching them to the appropriate per-channel linked list) and servicing requests for data from the transmit packet interface. the priority of service for each of the tasks is fixed by the tmac672 as follows: top priority is given to servicing ?expedited? read requests from the transmit hdlc processor / partial packet buffer block (thdl672). second priority is given to removing chains of data packets from the tdrr queue and attaching them to the appropriate per-channel linked list. third priority is given to servicing non-expedited read requests from the thdl672. 9.7.3 dma transaction controller the dma transaction controller coordinates the processing of requests from the thdl672 with the reading of data stored in host memory. the reading of a data packet may require a number of separate host memory transactions, interleaved with transactions of other dma channels. as well as reading data from the host master interface, the dma transaction controller initiates read and write transactions to the pci controller block (gpic) for the purposes of maintaining the data structures (queues, descriptors, etc.) in host memory. 9.7.4 read data pipeline the read data pipeline inserts delay in the data stream between the gpic interface and the thdl672 interface to enable the dma transaction controller to generate appropriate control signals at the transmit packet interface. 9.7.5 descriptor information cache the descriptor information cache provides the storage for the transmit channel descriptor reference (tcdr) table.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 77 9.7.6 free queue cache the free queue cache block implements the 6 element tdr free queue cache. caching tdrs reduces the number of host bus accesses that the tmac672 makes. tdrs are written to the cache one at a time as they are released by the tmac672. the cache is then flushed to host memory when it becomes full, when a td with the ioc bit set high is released, when the fqflush register bit is set high or when a td is released as the result of unprovisioning a channel. the cache controller may also flush the cache when it contains fewer than six elements or if the pointer index is within six elements of the end of the free queue. when the write pointer is near the end of the free queue, the cache controller writes only to the end of the queue and does not start writing from the top of the queue until the next time a flush is required. to do so would require two host memory transactions and would be of no benefit. 9.8 transmit hdlc controller / partial packet buffer the transmit hdlc controller / partial packet buffer block (thdl672) contains a partial packet buffer for pci latency control and a transmit hdlc controller. packet data retrieved from the pci host memory by the transmit dma controller block (tmac672) is stored in channel specific fifos residing in the partial packet buffer. when the amount of data in a fifo reaches a programmable threshold, the hdlc controller is enabled to initiate transmission. the hdlc controller performs flag generation, bit stuffing and, optionally, frame check sequence (fcs) insertion. the fcs is software selectable to be crc-ccitt or crc-32. the minimum packet size, excluding fcs, is two bytes. a single byte payload is illegal. the hdlc controller delivers data to the transmit channel assigner block (tcas672) on demand. a packet in progress is aborted if an under-run occurs. the thdl672 is prog rammable to operate in transparent mode where packet data retrieved from the pci host is transmitted verbatim. 9.8.1 transmit hdlc processor the hdlc processor is a time-slice state machine which can process up to 672 independent channels. the state vector and provisioning information for each channel is stored in a ram. whenever the tcas672 requests data, the appropriate state vector is read from the ram, processed and finally written back to the ram. the hdlc state-machine can be configured to perform flag insertion, bit stuffing and crc generation. the hdlc processor requests data from the partial packet processor whenever a request for channel data arrives. however, the hdlc processor does not start transmitting a packet until the entire packet is stored in the channel fifo or until the fifo free space is less than the
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 78 software programmable limit. if a c hannel fifo under-runs, the hdlc processor aborts the packet. the configuration of the hdlc processor is accessed using indirect channel read and write operations. when an indirect operation is performed, the information is accessed from ram during a null clock cycle inserted by the tcas672 block. writing new provisioning data to a channel resets the channel?s entire state vector. 9.8.2 transmit partial packet buffer processor the partial packet buffer processor controls the 32 kbyte partial packet ram which is divided into 16 byte blocks. a block pointer ram is used to chain the partial packet blocks into circular c hannel fifo buffers. thus, non-contiguous sections of ram can be allocated in the partial packet buffer ram to create a channel fifo. figure 16 shows an exampl e of three blocks (blocks 1, 3, and 200) linked together to form a 48 byte channel fifo. the three pointer values would be written sequentially using indirect block write accesses. when a channel is provisioned with this fifo, the state machine can be initialised to point to any one of the three blocks. the partial packet buffer processor is divided into three sections: reader, writer and roamer. the roamer is a time-sliced state machine which tracks each channel's fifo buffer free space and signals the writer to service a particular channel. the writer requests data from the tmac672 block and transfers packet data from the tmac672 to the associated channel fifo. the reader is a time- sliced state machine which transfers the hdlc information from a channel fifo to the hdlc processor when the hdlc processor requests it. if a buffer under- run occurs for a channel, the reader informs the hdlc processor and purges the rest of the packet.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 79 figure 16 ? partial packet buffer structure 16 bytes 16 bytes 16 bytes 16 bytes 16 bytes 16 bytes partial packet buffer ram block 2047 block 0 block 1 block 2 block 3 block 2047 block 0 block 1 block 2 block 3 block pointer ram block 200 block 200 0x03 0xc8 0x01 xx xx xx the writer and reader determine empty and full fifo conditions using flags. each block in the partial packet buffer has an associated flag. the writer sets the flag after the block is written and the reader clears the flag after the block is read. the flags are initialized (cleared) when the block pointers are written using indirect block writes. t he reader declares a channel fifo under-run whenever it tries to read data from a block without a set flag. the fifo algorithm of the partial packet buffer processor is based on per- channel software programmable transfer size and free space trigger level. instead of tracking the number of full blocks in a channel fifo, the processor tracks the number of empty blocks, called free space, as well as the number of end of packets stored in the fifo. recording the number of empty blocks instead of the number of full blocks r educes the amount of information the roamer must store in its state ram. the partial packet roamer records the fifo free space and end-of-packet count for all channel fifos. when the reader signals that a block has been read, the roamer increments the fifo free space and sets a per-channel request flag if
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 80 the free space is greater than the limit set by xfer[3:0]. the roamer also decrements the end-of-packet count when the reader signals that it has passed an end of a packet to the hdlc processor. if the hdlc is transmitting a packet and the fifo free space is greater than the starving trigger level and there are no complete packets within the fifo (end-of-packet count equal to zero), a per- channel starving flag is set. the roamer searches the starving flags in a round- robin fashion to decide which channel fifo should make expedited data requests to the tmac672 block. if no starving flags are set, the roamer searches the request flags in a round-robin fashion to decide which channel fifo should make regular data requests to the tmac672 block. the roamer informs the partial packet writer of the channel fifo to process, the fifo free space and the type of request it should make. the writer sends a request for data to the tmac672 block, writes the response data to the channel fifo, and sets the block full flags. the writer reports back to the roamer the number of blocks and end-of-packets transferred. the maximum amount of data transferred during one request is limited by a software programmable limit (xfer[3:0]). the configuration of the hdlc processor is accessed using indirect channel read and write operations as well as indirect block read and write operations. when an indirect operation is performed, the information is accessed from ram during a null clock cycle identified by the tcas672 block. writing new provisioning data to a channel resets the entire state vector. 9.9 transmit channel assigner the transmit channel assigner block (tcas672) processes up to 672 channels. data for all channels is sourced from a single byte-serial stream from the transmit hdlc controller / partial packet buffer block (thdl672). the tcas672 demultiplexes the data and assigns each byte to any one of 32 links. each link may be configured to support 2.048 or 8.192 h-mvip traffic, to support t1/j1/e1 channelised traffic or to support unchannelised traffic. when configured to support h-mvip traffic, each group of 8 links share a clock and frame pulse, otherwise each link is independent and has its own associated clock. for each high-speed link (td[2:0]), the tcas provides a six byte fifo. for the remaining links (td[31:3]), the tcas provides a single byte holding register. the tcas672 also performs parallel to serial conversion to form a bit- serial stream. in the event where multiple links are in need of data, tcas672 requests data from upstream blocks on a fixed priority basis with link td[0] having the highest priority and link td[31] the lowest. from the point of view of the tcas672, links configured for h-mvip traffic behave identically to links configured for t1/j1/e1 channelised or unchannelised traffic in the back end, only differing on the link side as described herein. first, the number of time-slots in each frame is programmable to be 32 or 128 and has
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 81 an associated data clock frequency that is double the data rate. this provides more bandwidth per link for applications requiring higher data densities on a single link. data at each time-slot may be independently assigned to be sourced from a different channel. second, h-mvip links reference the start of each frame with a frame pulse, thereby avoiding having to gap the link clock during the framing bits/bytes of each frame. the frame pulse is provided by an h-mvip bus master and ensures that all agents sharing the h-mvip bus remain synchronized. when configured for operation in 2.048 mbps h-mvip mode, the frame pulse is sampled using the same clock which samples the data. when configured for operation in 8.192 mbps h-mvip mode, the frame pulse is sampled using a separate frame pulse clock provided by an h-mvip bus master. the frame pulse clock has a synchronous timing relationship to the data clock. third, not all links are independent. when configured for operation in 2.048 mbps h-mvip mode, each group of 8 links share a clock and a frame pulse. links 0 through 7, 8 through 15, 16 through 23 and 24 through 31 each share a clock and a frame pulse. not all 8 links within each group need to be configured for operation in 2.048 mbps h-mvip mode. however, any link within each logical group of 8 which is configured for 2.048 mbps h-mvip operation will share the same clock and frame pulse. when configured for operation in 8.192 mbps h- mvip mode, links 4m (0 m 7) share a frame pulse, a data clock and a frame pulse clock. again, not all eight 4m (0 m 7) links need to be configured for operation in 8.192 mbps h-mvip mode, however, any link which is configured for 8.192 mbps h-mvip operation will share the same frame pulse, data clock and frame pulse clock. if link 4m is configured for 8.192 mbps h-mvip operation, then data transferred on that link is ?spread? over links 4m, 4m+1 4m+2 and 4m+3 from a channel assigner point of view. accordingly, when link 4m is configured for operation in 8.192 mbps h-mvip mode, links 4m+1, 4m+2 and 4m+3 must also be configured for operation in 8.192 mbps h-mvip mode. in the back end, the tcas672 extracts and processes the time-slots identically to channelised t1/j1/e1 traffic. links containing a t1/j1 or an e1 stream may be channelised. data at each time-slot may be independently assigned to be sourced from a different channel. the link clock is only active during time-slots 1 to 24 of a t1/j1 stream and is inactive during the frame bit. similarly, the clock is only active during time-slots 1 to 31 of an e1 stream and is inactive during the fas and nfas framing bytes. the most significant bit of time-slot 1 of a channelised link is identified by noting the absence of the clock and its re-activation. with knowledge of the transmit link and time-slot identity, the tcas672 performs a table look-up to identify the channel from which a data byte is to be sourced. links may also be unchannelised. then, all data bytes on that link belong to one channel. the tcas672 performs a table look-up to identify the channel to which a data byte belongs using only the outgoing link identity, as no time-slots are associated with unchannelised links. link clocks are no longer limited to t1/j1
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 82 or e1 rates and may range up to a maximum clock rate of 51.84 mhz for tclk[2:0] and 10 mhz for tclk[31:3]. the link clock is only active during bit times containing data to be transmitted and inactive during bits that are to be ignored by the downstream devices, such as framing and overhead bits. for the case of two unchannelised links, the maximum link rate is 51.84 mhz. for the case of more numerous unchannelised links or a mixture of channelised, unchannelised and h-mvip links, the total instantaneous link rate over all the links is limited to 64 mhz. 9.9.1 line interface translator (lit) the lit block translates the information between the 32 physical links and the line interface block. the lit block performs three functions: data translation, clock translation and frame pulse generation. when link 4m (0 m 7) is configured for operation in 8.192 mbps h-mvip mode, the lit block translates the data arriving from the line interface block on links 4m, 4m+1, 4m+2 and 4m+3 onto the 128 time-slot link 4m. the lit block translates data arriving from the line interface block on link 4m, 4m+1, 4m+2 and 4m+3 onto time-slots 0 through 31, 32 through 63, 64 through 95 and 96 through 127 respectively. when link 4m is configured for operation in 8.192 mbps h-mvip mode, outputs td[4m+3:4m+1] are driven with constant ones. however, links 4m+1, 4m+2 and 4m+3 must be programmed in the tcas672 link configuration register for 8.192 mbps h-mvip operation. when links are configured for operation in 2.048 mbps h-mvip mode, channelised t1/j1/e1 mode or unchannelised mode, the lit block does not perform any translation on the link data. when a link is configured for operation in h-mvip mode, the lit block divides the appropriate clock (tmvck[n] for 2.048 mbps h-mvip and tmv8dc for 8.192 mbps h-mvip) by two and provides this divided down clock to the line interface block. when a link is configured for operation in channelised t1/j1/e1 or unchannelised mode, the lit block does not perform any translation on the link clock. when a link is configured for operation in h-mvip mode, the lit block samples the appropriate frame pulse (tfpb[n] for 2.048 mbps h-mvip and tfp8b for 8.192 mbps h-mvip) and presents the sampled frame pulse to the line interface block. when a link is configured for operation in channelised t1/j1/e1 or unchannelised mode, the gapped clock is passed to the lit block unmodified. 9.9.2 line interface there are 32 identical line interface blocks in the tcas672. each line interface block contains 2 sub-bl ocks; one supporting channelised t1/j1/e1 streams and
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 83 the other h-mvip streams. based on c onfiguration, only one of the sub-blocks are active at one time; the other is held reset. each sub-block contains a bit counter, an 8-bit shift register and a holding register. each sub-block performs parallel to serial conversion. whenever the shift register is updated, a request for service is sent to the priority encoder block. when acknowledged by the priority encoder, the line interface would respond by writing the data into the holding register in the active sub-block. to support h-mvip links, each line interface block contains a time-slot counter. the time-slot counter is incremented each time the holding register is updated. when a frame pulse occurs, the time-slot counter is cleared to indicate that the next byte belongs to the first time-slot. to support non h-mvip channelised links, each line interface block contains a time-slot counter and a clock activity monitor. the time-slot counter is incremented each time the shift register is updated. the clock activity monitor is a counter that increments at the system clock (sysclk) rate and is cleared by a rising edge of the transmit clock (tclk[n]). a framing bit (t1/j1) or a framing byte (e1) is detected when the counter reaches a programmable threshold, at which point, the bit and time-slot counters are initialised to indicate that the next bit sampled is the most significant bit of the first time-slot. for unchannelised links, the time-slot counter and the clock activity monitor are held reset. 9.9.3 priority encoder the priority encoder monitors the line interfaces for requests and synchronises them to the sysclk timing domain. requests are serviced on a fixed priority scheme where highest to lowest priority is assigned from line interface td[0] to line interface td[31]. thus, simultaneous requests from line interface td[m] will be serviced ahead of line interface td[n], if m < n. the priority encoder selects the request from the link with the highest priority for service. when there are no pending requests, the priority encoder generates an idle cycle. in addition, once every fourth sysclk cycle, the priority encoder inserts a null cycle where no requests are serviced. this cycle is used by the channel assigner downstream for cbi accesses to the channel provision ram. 9.9.4 channel assigner the channel assigner block determines the channel number of the request currently being processed. the block contains a 1024 word channel provision ram. the address of the ram is constructed from concatenating the link number and the time-slot number of the highest priority requester. the fields of each ram word include the channel number and a time-slot enable flag. the time-slot enable flag labels the current time-slot as belonging to the channel indicted by the channel number field. for time-slots that are enabled, the
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 84 channel assigner issues a request to the thdl672 block which responds with packet data within one byte period of the transmit stream. 9.10 performance monitor the performance monitor block (pmon) contains four counters. the first two accumulate receive partial packet buffer fifo overrun events and transmit partial packet buffer fifo underflow events, respectively. the remaining two counters are software programmable to accumulate a variety of events, such as receive packet count, fcs error counts, etc. all counters saturate upon reaching maximum value. the accumulation logic consists of a counter and holding register pair. the counter is incremented when the associated event is detected. writing to the freedm-32p672 master clock / bert activity monitor and accumulation trigger register transfer the count to the corresponding holding register and clear the counter. the contents of the holding register is accessible via the pci interface. 9.11 jtag test access port interface the jtag test access port block provides jtag support for boundary scan. the standard jtag extest, sample, bypass, idcode and stctest instructions are supported. the freedm-32p672 identification code is 073800cd hexadecimal. 9.12 pci host interface the freedm-32p672 supports two different normal mode register types as defined below: 1. pci host accessible registers (pa) - these registers can be accessed through the pci host interface. 2. pci configuration registers (pc) - these register can only be accessed through the pci host interface during a pci configuration cycle. the pci registers are addressable on dword boundaries only. the pci offset shown in the table below must be combined with a base address to form the pci interface address. the base address can be found in the freedm-32p672 memory base address register in the pci configuration memory space. table 12 ? normal mode pci host accessible register memory map pci offset register 0x000 freedm-32p672 master reset
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 85 pci offset register 0x004 freedm-32p672 master interrupt enable 0x008 freedm-32p672 master interrupt status 0x00c freedm-32p672 master clock / frame pulse / bert activity monitor and accumulation trigger 0x010 freedm-32p672 master link activity monitor 0x014 freedm-32p672 master line loopback #1 0x018 freedm-32p672 master line loopback #2 0x01c freedm-32p672 reserved 0x020 freedm-32p672 master bert control 0x024 freedm-32p672 master performance monitor control 0x028 - 0x07c reserved 0x080 gpic control 0x084 - 0x0fc gpic reserved 0x100 rcas indirect channel and time-slot select 0x104 rcas indirect channel data 0x108 rcas framing bit threshold 0x10c rcas channel disable 0x110 - 0x17c rcas reserved 0x180 ? 0x1fc rcas link #0 through #31 configuration 0x200 rhdl indirect channel select 0x204 rhdl indirect channel data register #1 0x208 rhdl indirect channel data register #2 0x20c rhdl reserved 0x210 rhdl indirect block select 0x214 rhdl indirect block data register 0x218 - 0x21c rhdl reserved 0x220 rhdl configuration 0x224 rhdl maximum packet length 0x228 - 0x23c rhdl reserved
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 86 pci offset register 0x240 - 0x27c reserved 0x280 rmac control 0x284 rmac indirect channel provisioning 0x288 rmac packet descriptor table base lsw 0x28c rmac packet descriptor table base msw 0x290 rmac queue base lsw 0x294 rmac queue base msw 0x298 rmac packet descriptor reference large buffer free queue start 0x29c rmac packet descriptor reference large buffer free queue write 0x2a0 rmac packet descriptor reference large buffer free queue read 0x2a4 rmac packet descriptor reference large buffer free queue end 0x2a8 rmac packet descriptor reference small buffer free queue start 0x2ac rmac packet descriptor reference small buffer free queue write 0x2b0 rmac packet descriptor reference small buffer free queue read 0x2b4 rmac packet descriptor reference small buffer free queue end 0x2b8 rmac packet descriptor reference ready queue start 0x2bc rmac packet descriptor reference ready queue write 0x2c0 rmac packet descriptor reference ready queue read 0x2c4 rmac packet descriptor reference ready queue end 0x2c8 - 0x2fc rmac reserved 0x300 tmac control 0x304 tmac indirect channel provisioning 0x308 tmac descriptor table base lsw
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 87 pci offset register 0x30c tmac descriptor table base msw 0x310 tmac queue base lsw 0x314 tmac queue base msw 0x318 tmac descriptor reference free queue start 0x31c tmac descriptor reference free queue write 0x320 tmac descriptor reference free queue read 0x324 tmac descriptor reference free queue end 0x328 tmac descriptor reference ready queue start 0x32c tmac descriptor reference ready queue write 0x330 tmac descriptor reference ready queue read 0x334 tmac descriptor reference ready queue end 0x338 - 0x37c tmac reserved 0x380 thdl indirect channel select 0x384 thdl indirect channel data #1 0x388 thdl indirect channel data #2 0x38c thdl indirect channel data #3 0x390 - 0x39c thdl reserved 0x3a0 thdl indirect block select 0x3a4 thdl indirect block data 0x3a8 - 0x3ac thdl reserved 0x3b0 thdl configuration 0x3b4 - 0x3bc thdl reserved 0x3c0 - 0x3fc reserved 0x400 tcas indirect channel and time-slot select 0x404 tcas indirect channel data 0x408 tcas framing bit threshold 0x40c tcas idle time-slot fill data 0x410 tcas channel disable 0x414 - 0x47c tcas reserved
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 88 pci offset register 0x480 - 0x4fc tcas link #0 through #31 configuration 0x500 pmon status 0x504 pmon receive fifo overflow count 0x508 pmon transmit fifo underflow count 0x50c pmon configurable count #1 0x510 pmon configurable count #2 0x514 - 0x51c pmon reserved 0x520 - 0x7fc reserved the following pci configuration registers are implemented by the pci interface. these registers can only be accessed when the pci interface is a target and a configuration cycle is in progress as indicated using the idsel input. table 13 ? pci configuration register memory map pci offset register 0x00 vendor identification/device identification 0x04 command/status 0x08 revision identifier/class code 0x0c cache line size/latency timer/header type/bist 0x10 cbi memory base address register 0x14 - 0x24 unused base address register 0x28 - 0x38 reserved 0x3c interrupt line/interrupt pin/min_gnt/max_lat
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 89 10 normal mode register description normal mode registers are used to configure and monitor the operation of the freedm-32p672. notes on normal mode register bits: 1. writing values into unused register bits has no effect. however, to ensure software compatibility with future, f eature-enhanced versions of the product, unused register bits must be written with logic zero. reading back unused bits can produce either a logic one or a logic zero; hence, unused register bits should be masked off by software when read. 2. except where noted, all configuration bits that can be written into can also be read back. this allows the proc essor controlling the freedm-32p672 to determine the programming state of the block. 3. writable normal mode register bits are cleared to logic zero upon reset unless otherwise noted. 4. writing into read-only normal mode register bit locations does not affect freedm-32p672 operation unless otherwise noted. 5. certain register bits are reserved. these bits are associated with megacell functions that are unused in this application. to ensure that the freedm- 32p672 operates as intended, reserved register bits must only be written with their default values. similarly, writing to reserved registers should be avoided. 10.1 pci host accessible registers pci host accessible registers can be accessed by the pci host. for each register description below, the hexadecimal register number indicates the pci offset from the base address in the freedm-32p672 cbi register base address register when accesses are made using the pci host port. note these registers are not byte addressable. writing to any one of these registers modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to the register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 90 register 0x000 : freedm-32p672 master reset bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w reset 0 bit 14 to bit 0 unused xxxxh this register provides software reset capability. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. reset: the reset bit allows the freedm-32p672 to be reset under software control. if the reset bit is a logic one, the entire freedm-32p672 except the pci interface is held in reset. this bit is not self-clearing. therefore, a logic zero must be written to bring the freedm-32p672 out of reset. holding the freedm-32p672 in a reset state places it into a low power, stand-by mode. a hardware reset clears the reset bit, thus negating the software reset. note unlike the hardware reset input (rstb), reset does not force the freedm- 32p672's pci pins tristate. transmit link data pins (td[31:0]) are forced high. in addition, all registers except the gpic pci configuration registers, are reset to their default values.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 91 register 0x004 : freedm-32p672 master interrupt enable bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tfudre 0 bit 14 r/w ioce 0 bit 13 r/w tdfqee 0 bit 12 r/w tdqrdye 0 bit 11 r/w tdqfe 0 bit 10 r/w rpdrqee 0 bit 9 r/w rpdfqee 0 bit 8 r/w rpqrdye 0 bit 7 r/w rpqlfe 0 bit 6 r/w rpqsfe 0 bit 5 r/w rfovre 0 bit 4 r/w rpfee 0 bit 3 r/w rabrte 0 bit 2 r/w rfcsee 0 bit 1 r/w perre 0 bit 0 r/w serre 0 this register provides interrupt enables for various events detected or initiated by the freedm-32p672. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 92 serre: the system error interrupt enable bit (serre) enables pci system error interrupts to the pci host. when serre is set high, any address parity error, data parity error on special cycle commands, reception of a master abort or detection of a target abort will cause an interrupt to be generated on the pciintb output. interrupts are masked when serre is set low. however, the serri bit remains valid when interrupts are disabled and may be polled to detect pci system error events. perre: the parity error interrupt enable bit (perre) enables pci parity error interrupts to the pci host. when perre is set high, data parity errors detected by the freedm-32p 672 or parity errors reported by a target will cause an interrupt to be generated on the pciintb output. interrupts are masked when perre is set low. however, the perri bit remains valid when interrupts are disabled and may be polled to detect pci parity error events. rfcsee: the receive frame check sequence error interrupt enable bit (rfcsee) enables receive fcs error interrupts to the pci host. when rfcsee is set high, a mismatch between the received fcs code and the computed crc residue will cause an interrupt to be generated on the pciintb output. interrupts are masked when rfcsee is set low. however, the rfcsei bit remains valid when interrupts are disabled and may be polled to detect receive fcs error events. rabrte: the receive abort interrupt enable bit (rabrte) enables receive hdlc abort interrupts to the pci host. when rabrte is set high, receipt of an abort code (at least 7 contiguous 1's) will caus e an interrupt to be generated on the pciintb output. interrupts are masked when rabrte is set low. however, the rabrti bit remains valid when interrupts are disabled and may be polled to detect receive abort events. rpfee: the receive packet format error interrupt enable bit (rpfee) enables receive packet format error interrupts to the pci host. when rpfee is set high, receipt of a packet that is longer than the maximum specified in the rhdl maximum packet length register, of a packet that is shorter than 32 bits (crc-ccitt) or 48 bits (crc-32), or of a packet that is not octet aligned will cause an interrupt to be generated on the pciintb output. interrupts are masked when rpfee is set low. however, the rpfei bit remains valid when
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 93 interrupts are disabled and may be polled to detect receive packet format error events. rfovre: the receive fifo overrun error interrupt enable bit (rfovre) enables receive fifo overrun error interrupts to the pci host. when rfovre is set high, attempts to write data into the logical fifo of a channel when it is already full will cause an interrupt to be generated on the pciintb output. interrupts are masked when rfovre is set low. however, the rfovri bit remains valid when interrupts are disabled and may be polled to detect receive fifo overrun events. rpqsfe: the receive packet descriptor small buffer free queue cache read interrupt enable bit (rpqsfe) enables receive packet descriptor small free queue cache read interrupts to the pci host. when rpqsfe is set high, reading a programmable number of rpdr blocks fr om the rpdr small buffer free queue will cause an interrupt to be generated on the pciintb output. interrupts are masked when rpqsfe is set low. however, the rpqsfi bit remains valid when interrupts are disabled and may be polled to detect rpdr small buffer free queue cache read events. rpqlfe: the receive packet descriptor large buffer free queue cache read interrupt enable bit (rpqlfe) enables receive packet descriptor large free queue cache read interrupts to the pci host. when rpqlfe is set high, reading a programmable number of rpdr blocks from the rpdr large buffer free queue will cause an interrupt to be generated on the pciintb output. interrupts are masked when rpqlfe is set low. however, the rpqlfi bit remains valid when interrupts are disabled and may be polled to detect rpdr large buffer free queue cache read events. rpqrdye: the receive packet descriptor ready queue write interrupt enable bit (rpqrdye) enables receive packet descriptor ready queue write interrupts to the pci host. when rpqrdye is set high, writing a programmable number of rpdrs to the rpdr ready queue will cause an interrupt to be generated on the pciintb output. interrupts are masked when rpqrdye is set low. however, the rpqrdyi bit remains valid when interrupts are disabled and may be polled to detect rpdr ready queue write events.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 94 rpdfqee: the receive packet descriptor free queue error interrupt enable bit (rpdfqee) enables receive packet descriptor free queue error interrupts to the pci host. when rpdfqee is set high, attempts to retrieve an rpdr when both the large buffer and small buffer free queues are empty will cause an interrupt to be generated on the pciintb output. interrupts are masked when rpdfqee is set low. however, the rpdfqei bit remains valid when interrupts are disabled and may be polled to detect rpdr free queue empty error events. rpdrqee: the receive packet descriptor ready queue error interrupt enable bit (rpdrqee) enables receive packet descriptor ready queue error interrupts to the pci host. when rpdrqee is set high, attempts to write an rpdr when ready queue is ready full will caus e an interrupt to be generated on the pciintb output. interrupts are masked when rpdrqee is set low. however, the rpdrqei bit remains valid when interrupts are disabled and may be polled to detect rpdr ready queue full error events. tdqfe: the transmit packet descriptor free queue write interrupt enable bit (tdqfe) enables transmit packet descriptor free queue write interrupts to the pci host. when tdqfe is set high, writing a programmable number of tdrs to the tdr free queue will cause an interrupt to be generated on the pciintb output. interrupts are masked when tdqfe is set low. however, the tdqfi bit remains valid when interrupts are disabled and may be polled to detect tdr free queue write events. tdqrdye: the transmit descriptor ready queue cache read interrupt enable bit (tdqrdye) enables transmit descriptor ready queue cache read interrupts to the pci host. when tdqrdye is set high, reading a programmable number of tdrs from the tdr ready queue will cause an interrupt to be generated on the pciintb output. interrupts are masked when tdqrdye is set low. however, the tdqrdyi bit remains valid when interrupts are disabled and may be polled to detect tdr ready queue cache read events. tdfqee: the transmit descriptor free queue error interrupt enable bit (tdfqee) enables transmit descriptor free queue error interrupts to the pci host. when tdfqee is set high, attempting to write to the transmit free queue while the queue is full will cause an interrupt to be generated on the pciintb output. interrupts are masked when tdfqee is set low. however, the tdfqei bit
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 95 remains valid when interrupts are disabled and may be polled to detect td free queue error events. ioce: the transmit interrupt on complete enable bit (ioce) enables transmission complete interrupts to the pci host. when ioce is set high, complete transmission of a packet with the ioc bit in the td set high will cause an interrupt to be generated on the pciintb output. interrupts are masked when ioce is set low. however, the ioci bit remains valid when interrupts are disabled and may be polled to detect transmission of ioc tagged packets. tfudre: the transmit fifo underflow error in terrupt enable bit (tfudre) enables transmit fifo underflow error interrupt s to the pci host. when tfudre is set high, attempts to read data from the logical fifo when it is already empty will cause an interrupt to be generated on the pciintb output. interrupts are masked when tfudre is set low. however, the tfudri bit remains valid when interrupts are disabled and may be polled to detect transmit fifo underflow events.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 96 register 0x008 : freedm-32p672 master interrupt status bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r tfudri x bit 14 r ioci x bit 13 r tdfqei x bit 12 r tdqrdyi x bit 11 r tdqfi x bit 10 r rpdrqei x bit 9 r rpdfqei x bit 8 r rpqrdyi x bit 7 r rpqlfi x bit 6 r rpqsfi x bit 5 r rfovri x bit 4 r rpfei x bit 3 r rabrti x bit 2 r rfcsei x bit 1 r perri x bit 0 r serri x this register reports the interrupt status for various events detected or initiated by the freedm-32p672. reading this registers acknowledges and clears the interrupts. note this register is not byte addressable. reading this register clears all the interrupt bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 97 serri: the system error interrupt status bit (serri) reports pci system error interrupts to the pci host. serri is set high upon detection of any address parity error, data parity error on special cycle commands, reception of a master abort or detection of a target abort event. the serri bit remains valid when interrupts are disabled and may be polled to detect pci system error events. perri: the parity error interrupt status bit (perri) reports pci parity error interrupts to the pci host. perri is set high when data parity errors are detected by the freedm-32p672 while acting as a master, and when parity errors are reported to the freedm-32p672 by a target via the perrb input. the perri bit remains valid when interrupts are disabled and may be polled to detect pci parity error events. rfcsei: the receive frame check sequence error interrupt status bit (rfcsei) reports receive fcs error interrupts to the pci host. rfcsei is set high, when a mismatch between the received fcs code and the computed crc residue is detected. rfcsei remains valid when interrupts are disabled and may be polled to detect receive fcs error events. rabrti: the receive abort interrupt status bit (rabrti) reports receive hdlc abort interrupts to the pci host. rabrti is set high upon receipt of an abort code (at least 7 contiguous 1's). rabrti remains valid when interrupts are disabled and may be polled to detect receive abort events. rpfei: the receive packet format error interrupt status bit (rpfei) reports receive packet format error interrupts to the pci host. rpfei is set high upon receipt of a packet that is longer than the maximum programmed length, of a packet that is shorter than 32 bits (crc-ccitt) or 48 bits (crc-32) , or of a packet that is not octet aligned. rpfei remains valid when interrupts are disabled and may be polled to detect receive packet format error events. rfovri: the receive fifo overrun error interrupt status bit (rfovri) reports receive fifo overrun error interrupts to the pci host. rfovri is set high on attempts to write data into the logical fifo of a channel when it is already full. rfovri remains valid when interrupts are disabled and may be polled to detect receive fifo overrun events.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 98 rpqsfi: the receive packet descriptor small buffer free queue cache read interrupt status bit (rpqsfi) reports receive packet descriptor small free queue cache read interrupts to the pci host. rpqsfi is set high when the programmable number of rpdr blocks is read from the rpdr small buffer free queue. rpqsfi remains valid when interrupts are disabled and may be polled to detect rpdr small buffer free queue cache read events. rpqlfi: the receive packet descriptor large buffer free queue cache read interrupt status bit (rpqlfi) reports receive packet descriptor large free queue cache read interrupts to the pci host. rpqlfi is set high when the programmable number of rpdr blocks is read from the rpdr large buffer free queue. rpqlfi remains valid when interrupts are disabled and may be polled to detect rpdr large buffer free queue cache read events. rpqrdyi: the receive packet descriptor ready queue write interrupt status bit (rpqrdyi) reports receive packet descriptor ready queue write interrupts to the pci host. rpqrdyi is set high when the programmable number of rpdrs is written to the rpdr ready queue. rpqrdyi remains valid when interrupts are disabled and may be polled to detect rpdr ready queue write events. rpdfqei: the receive packet descriptor free queue error interrupt status bit (rpdfqei) reports receive packet descriptor free queue error interrupts to the pci host. rpdfqei is set high upon attempts to retrieve an rpdr when both the large buffer and small buffer free queues are empty. rpdfqei remains valid when interrupts are disabled and may be polled to detect rpdr free queue empty error events. rpdrqei: the receive packet descriptor ready queue error interrupt status bit (rpdrqei) reports receive packet descriptor ready queue error interrupts to the pci host. rpdrqei is set high upon attempts to write an rpdr when ready queue is ready full. rpdrqei remains valid when interrupts are disabled and may be polled to detect rpdr ready queue full error events. tdqfi: the transmit packet descriptor free queue write interrupt status bit (tdqfi) reports transmit packet descriptor free queue write interrupts to the pci host. tdqfi is set high when the programmable number of tdrs is written to the
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 99 tdr free queue. tdqfi remains valid when interrupts are disabled and may be polled to detect tdr free queue write events. tdqrdyi: the transmit descriptor ready queue cache read interrupt status bit (tdqrdyi) reports transmit descriptor ready queue cache read interrupts to the pci host. tdqrdyi is set high when the programmable number of tdrs is read from the tdr ready queue. tdqrdyi remains valid when interrupts are disabled and may be polled to detect tdr ready queue cache read events. tdfqei: the transmit descriptor free queue error interrupt status bit (tdfqei) reports transmit descriptor free queue error interrupts to the pci host. tdfqei is set high when an attempt to write to the transmit free queue fail due to the queue being already full. tdfqei bit remains valid when interrupts are disabled and may be polled to detect td free queue error events. ioci: the transmit interrupt on complete status bit (ioci) reports transmission complete interrupts to the pci host. ioci is set high, when a packet with the ioc bit in the td set high is complete ly transmitted. ioci remains valid when interrupts are disabled and may be polled to detect transmission of ioc tagged packets. tfudri: the transmit fifo underflow error inte rrupt status bit (tfudri) reports transmit fifo underflow error interrupts to the pci host. tfudri is set high upon attempts to read data from the logical fifo when it is already empty. tfudri remains valid when interrupt s are disabled and may be polled to detect transmit fifo underflow events.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 100 register 0x00c : freedm-32p672 master clock / frame pulse / bert activity monitor and accumulation trigger bit type func tion default bit 31 to bit 12 unused xxxxxh bit 11 r tfpa[3] x bit 10 r tfpa[2] x bit 9 r tfpa[1] x bit 8 r tfpa[0] x bit 7 r rfpa[3] x bit 6 r rfpa[2] x bit 5 r rfpa[1] x bit 4 r rfpa[0] x bit 3 r tfp8a x bit 2 r rfp8a x bit 1 r tbda x bit 0 r sysclka x this register provides activity monitoring on freedm-32p672 system clock, h-mvip frame pulse and bert port inputs. when a monitored input makes a transition, the corresponding re gister bit is set high. the bit will remain high until this register is read, at which point, all the bits in this register are cleared. a lack of transitions is indicated by the corresponding register bit reading low. this register should be read periodically to detect for stuck at conditions. writing to this register delimits the accumulation intervals in the pmon accumulation registers. counts accumulated in those registers are transferred to holding registers where they can be read. the counters themselves are then cleared to begin accumulating events for a new accumulation interval. the bits in this register are not affected by write accesses. note this register is not byte addressable. reading this register clears all the activity bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 101 implemented. however, when all four byte enables are negated, no access is made to this register. sysclka: the system clock active bit (sysclka) monitors for low to high transitions on the sysclk input. sysclka is set high on a rising edge of sysclk, and is set low when this register is read. tbda: the transmit bert data active bit (tbda) monitors for low to high transitions on the tbd input. tbda is set high on a rising edge of tdb, and is set low when this register is read. rfp8a: the receive 8.192 mbps h-mvip frame pulse activity bit (rfp8a) monitors for low to high transitions on the rfp8b input. rfp8a is set high when rfp8b has been sampled low and sampled high by falling edges of the rmv8fpc, and is set low when this register is read. tfp8a: the transmit 8.192 mbps h-mvip frame pulse activity bit (tfp8a) monitors for low to high transitions on the tfp8b input. tfp8a is set high when tfp8b has been sampled low and sampled high by falling edges of the tmv8fpc, and is set low when this register is read. rfpa[3:0]: the receive frame pulse activity bits (rfpa[3:0]) monitor for low to high transitions on the rfpb[3:0] inputs. rfpa[n] is set high when rfpb[n] has been sampled low and sampled high by falling edges of the corresponding rmvck[n], and is set low when this register is read. tfpa[3:0]: the transmit frame pulse activity bits (tfpa[3:0]) monitor for low to high transitions on the tfpb[3:0] inputs. tfpa[n] is set high when tfpb[n] has been sampled low and sampled high by falling edges of the corresponding tmvck[n], and is set low when this register is read.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 102 register 0x010 : freedm-32p672 master link activity monitor bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r tlga[7] x bit 14 r tlga[6] x bit 13 r tlga[5] x bit 12 r tlga[4] x bit 11 r tlga[3] x bit 10 r tlga[2] x bit 9 r tlga[1] x bit 8 r tlga[0] x bit 7 r rlga[7] x bit 6 r rlga[6] x bit 5 r rlga[5] x bit 4 r rlga[4] x bit 3 r rlga[3] x bit 2 r rlga[2] x bit 1 r rlga[1] x bit 0 r rlga[0] x this register provides activity monitoring on freedm-32p672 receive and transmit link inputs. when a monitored input makes a low to high transition, the corresponding register bit is set high. the bit will remain high until this register is read, at which point, all the bits in this register are cleared. a lack of transitions is indicated by the corresponding register bit reading low. this register should be read periodically to detect for stuck at conditions. note this register is not byte addressable. reading this register clears all the activity bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 103 implemented. however, when all four byte enables are negated, no access is made to this register. rlga[0]: the receive link group #0 active bit (rlga[0]) monitors for transitions on the rd[3:0] and rclk[3:0]/rmvck[0]/rmv8dc inputs. rlga[0] is set high when either: 1. each of rd[3:0] has been sampled low and sampled high by rising edges of the corresponding rclk[3:0] inputs, or 2. each of rd[3:0] has been sampled low and sampled high by rising edges of the rmvck[0] input, or 3. rd[0] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[0] is set low when this register is read. rlga[1]: the receive link group #1 active bit (rlga[1]) monitors for transitions on the rd[7:4] and rclk[7:4]/rmvck[0]/rmv8dc inputs. rlga[1] is set high when either: 1. each of rd[7:4] has been sampled low and sampled high by rising edges of the corresponding rclk[7:4] inputs, or 2. each of rd[7:4] has been sampled low and sampled high by rising edges of the rmvck[0] input, or 3. rd[4] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[1] is set low when this register is read. rlga[2]: the receive link group #2 active bit (rlga[2]) monitors for transitions on the rd[11:8] and rclk[11:8]/rmvck[1]/rmv8dc inputs. rlga[2] is set high when either: 1. each of rd[11:8] has been sampled low and sampled high by rising edges of the corresponding rclk[11:8] inputs, or 2. each of rd[11:8] has been sampled low and sampled high by rising edges of the rmvck[1] input, or 3. rd[8] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[2] is set low when this register is read. rlga[3]: the receive link group #3 active bit (rlga[3]) monitors for transitions on the rd[15:12] and rclk[15:12]/rmvck[1]/rmv8dc inputs. rlga[3] is set high when either:
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 104 1. each of rd[15:12] has been sampled low and sampled high by rising edges of the corresponding rclk[15:12] inputs, or 2. each of rd[15:12] has been sampled low and sampled high by rising edges of the rmvck[1] input, or 3. rd[12] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[3] is set low when this register is read. rlga[4]: the receive link group #4 active bit (rlga[4]) monitors for transitions on the rd[19:16] and rclk[19:16]/rmvck[2]/rmv8dc inputs. rlga[4] is set high when either: 1. each of rd[19:16] has been sampled low and sampled high by rising edges of the corresponding rclk[19:16] inputs, or 2. each of rd[19:16] has been sampled low and sampled high by rising edges of the rmvck[2] input, or 3. rd[16] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[4] is set low when this register is read. rlga[5]: the receive link group #5 active bit (rlga[5]) monitors for transitions on the rd[23:20] and rclk[23:20]/rmvck[2]/rmv8dc inputs. rlga[5] is set high when either: 1. each of rd[23:20] has been sampled low and sampled high by rising edges of the corresponding rclk[23:20] inputs, or 2. each of rd[23:20] has been sampled low and sampled high by rising edges of the rmvck[2] input, or 3. rd[20] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[5] is set low when this register is read. rlga[6]: the receive link group #6 active bit (rlga[6]) monitors for transitions on the rd[27:24] and rclk[27:24]/rmvck[3]/rmv8dc inputs. rlga[6] is set high when either: 1. each of rd[27:24] has been sampled low and sampled high by rising edges of the corresponding rclk[27:24] inputs, or 2. each of rd[27:24] has been sampled low and sampled high by rising edges of the rmvck[3] input, or 3. rd[24] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[6] is set low when this register is read.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 105 rlga[7]: the receive link group #7 active bit (rlga[7]) monitors for transitions on the rd[31:28] and rclk[31:28]/rmvck[3]/rmv8dc inputs. rlga[7] is set high when either: 1. each of rd[31:28] has been sampled low and sampled high by rising edges of the corresponding rclk[31:28] inputs, or 2. each of rd[31:28] has been sampled low and sampled high by rising edges of the rmvck[3] input, or 3. rd[28] has been sampled low and sampled high by rising edges of the rmv8dc input. rlga[7] is set low when this register is read. tlga[0]: the transmit link group #0 active bit (tlga[0]) monitors for low to high transitions on the tclk[3:0] & tmvck[0] inputs. tlga[0] is set high when either: 1. rising edges have been observed on all four tclk[3:0] inputs, or 2. a rising edge has been observed on the tmvck[0] input. tlga[0] is set low when this register is read. tlga[1]: the transmit link group #1 active bit (tlga[1]) monitors for low to high transitions on the tclk[7:4] & tmvck[1] inputs. tlga[1] is set high when either: 1. rising edges have been observed on all four tclk[7:4] inputs, or 2. a rising edge has been observed on the tmvck[1] input. tlga[1] is set low when this register is read. tlga[2]: the transmit link group #2 active bit (tlga[2]) monitors for low to high transitions on the tclk[11:8] & tmvck[2] inputs. tlga[2] is set high when either: 1. rising edges have been observed on all four tclk[11:8] inputs, or 2. a rising edge has been observed on the tmvck[2] input. tlga[2] is set low when this register is read. tlga[3]: the transmit link group #3 active bit (tlga[3]) monitors for low to high transitions on the tclk[15:12] & tmvck[3] inputs. tlga[3] is set high when either: 1. rising edges have been observed on all four tclk[15:12] inputs, or 2. a rising edge has been observed on the tmvck[3] input. tlga[3] is set low when this register is read.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 106 tlga[4]: the transmit link group #4 active bit (tlga[4]) monitors for low to high transitions on the tclk[19:16] inputs. tlga[4] is set high when rising edges have been observed on all four tclk[19:16] inputs, and is set low when this register is read. tlga[5]: the transmit link group #5 active bit (tlga[5]) monitors for low to high transitions on the tclk[23:20] inputs. tlga[5] is set high when rising edges have been observed on all four tclk[23:20] inputs, and is set low when this register is read. tlga[6]: the transmit link group #6 active bit (tlga[6]) monitors for low to high transitions on the tclk[27:24] inputs. tlga[6] is set high when rising edges have been observed on all four tclk[27:24] inputs, and is set low when this register is read. tlga[7]: the transmit link group #7 active bit (tlga[7]) monitors for low to high transitions on the tclk[31:28] & tmv8dc inputs. tlga[7] is set high when either: 1. rising edges have been observed on all four tclk[31:28] inputs, or 2. a rising edge has been observed on the tmv8dc input. tlga[7] is set low when this register is read.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 107 register 0x014 : freedm-32p 672 master line loopback #1 bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w llben[15] 0 bit 14 r/w llben[14] 0 bit 13 r/w llben[13] 0 bit 12 r/w llben[12] 0 bit 11 r/w llben[11] 0 bit 10 r/w llben[10] 0 bit 9 r/w llben[9] 0 bit 8 r/w llben[8] 0 bit 7 r/w llben[7] 0 bit 6 r/w llben[6] 0 bit 5 r/w llben[5] 0 bit 4 r/w llben[4] 0 bit 3 r/w llben[3] 0 bit 2 r/w llben[2] 0 bit 1 r/w llben[1] 0 bit 0 r/w llben[0] 0 this register controls line loopback for links #0 to #15. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. llben[15:0]: the line loopback enable bits (llben[15:0]) controls line loopback for links #15 to #0. when links #0 through #15 are configured for channelised
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 108 t1/j1/e1 or unchannelised traffic and llben[n] is set high, the data on rd[n] is passed verbatim to td[n] which is then updated on the falling edge of rclk[n]. tclk[n] is ignored. when llben[n] is set low, td[n] is processed normally. line loopback is not supported for h-mvip traffic.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 109 register 0x018 : freedm-32p 672 master line loopback #2 bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w llben[31] 0 bit 14 r/w llben[30] 0 bit 13 r/w llben[29] 0 bit 12 r/w llben[28] 0 bit 11 r/w llben[27] 0 bit 10 r/w llben[26] 0 bit 9 r/w llben[25] 0 bit 8 r/w llben[24] 0 bit 7 r/w llben[23] 0 bit 6 r/w llben[22] 0 bit 5 r/w llben[21] 0 bit 4 r/w llben[20] 0 bit 3 r/w llben[19] 0 bit 2 r/w llben[18] 0 bit 1 r/w llben[17] 0 bit 0 r/w llben[16] 0 this register controls line loopback for links #16 to #31. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. llben[31:16]: the line loopback enable bits (llben[31:16]) controls line loopback for links #31 to #16. when links #16 through #31 are configured for channelised
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 110 t1/j1/e1 or unchannelised traffic and llben[n] is set high, the data on rd[n] is passed verbatim to td[n] which is then updated on the falling edge of rclk[n]. tclk[n] is ignored. when llben[n] is set low, td[n] is processed normally. line loopback is not supported for h-mvip traffic.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 111 register 0x01c : freedm-32p672 reserved bit type func tion default bit 15 to bit 1 unused xxxxh bit 0 r/w reserved 0 note this register is not byte addressable. reading this register clears all the activity bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. reserved: the reserved bit must be set low for correct operation of the freedm- 32p672 device.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 112 register 0x020 : freedm-32p672 master bert control bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tben 0 bit 14 unused x bit 13 unused x bit 12 r/w tbsel[4] 0 bit 11 r/w tbsel[3] 0 bit 10 r/w tbsel[2] 0 bit 9 r/w tbsel[1] 0 bit 8 r/w tbsel[0] 0 bit 7 r/w rben 0 bit 6 unused x bit 5 unused x bit 4 r/w rbsel[4] 0 bit 3 r/w rbsel[3] 0 bit 2 r/w rbsel[2] 0 bit 1 r/w rbsel[1] 0 bit 0 r/w rbsel[0] 0 this register controls the bit error rate testing of the receive and transmit links. bit error rate testing is not supported for links configured for h-mvip traffic. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 113 rbsel[4:0]: the receive bit error rates testing link select bits (rbsel[4:0]) controls the source of data on the rbd and rbclk outputs when receive bit error rate testing is enabled (rben set high). rbsel[4:0] is a binary number that selects a receive link configured for non h-mvip traffic (rd[31:0]/rclk[31:0]) to be the source of data for rbd and rbclk outputs. rbsel[4:0] is ignored when rben is set low. rbsel[4:0] cannot select a link configured for h- mvip traffic. rben: the receive bit error rates testing link enable bit (rben) controls the receive bit error rate testing port. when rben is set high, rbsel[4:0] is a binary number that selects a receive link configured for non h-mvip traffic (rd[31:0]/rclk[31:0]) to be the source of data for rbd and rbclk outputs. when rben is set low, rbd and rbclk are held tristated. tbsel[4:0]: the transmit bit error rates testing link select bits (tbsel[4:0]) controls the over-writing of transmit data on td[31:0] by data on tbd when transmit bit error rate testing is enabled (tben set high) and the selected link is not in line loopback (llben[n] set low). tbsel[4:0] is a binary number that selects a transmit link configured for non h-mvip traffic (td[31:0]/tclk[31:0]) to carry the data on tbd. the tbclk output is a buffered version of the selected one of tclk[31:0]. tbsel[4:0] is ignored when tben is set low. tbsel[4:0] cannot select a link configured for h-mvip traffic. tben: the transmit bit error rates testing link enable bit (tben) controls the transmit bit error rate testing port. when tben is set high and the associated link in not in line loopback (llben set low), tbsel[4:0] is a binary number that selects a transmit link data configured for non h-mvip traffic (td[31:0]) to carry the data on tbd and selects a transmit link clock (tclk[31:0]) as the source of tbclk. when tben is set low, all transmit links are processed normally and tbclk is held tristated.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 114 register 0x024 : freedm-32p672 master performance monitor control bit type func tion default bit 31 to bit 15 unused xxxxxh bit 14 r/w tp2en 0 bit 13 r/w tabrt2en 0 bit 12 r/w rp2en 0 bit 11 r/w rlene2en 0 bit 10 r/w rabrt2en 0 bit 9 r/w rfcse2en 0 bit 8 r/w rspe2en 0 bit 7 unused x bit 6 r/w tp1en 0 bit 5 r/w tabrt1en 0 bit 4 r/w rp1en 0 bit 3 r/w rlene1en 0 bit 2 r/w rabrt1en 0 bit 1 r/w rfcse1en 0 bit 0 r/w rspe1en 0 this register configures the events that are accumulated in the two configurable performance monitor counters in the pmon block. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. rspe1en: the receive small packet error accumulate enable bit (rspe1en) enables counting of minimum packet size violation events. when rspe1en is set
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 115 high, receipt of a packet that is shor ter than 32 bits (crc-ccitt, unspecified crc or no crc) or 48 bits (crc-32) will cause the pmon configurable accumulator #1 register to increment. small packet errors are ignored when rspe1en is set low. rfcse1en: the receive frame check sequence error accumulate enable bit (rfcse1en) enables counting of receive fcs error events. when rfcse1en is set high, a mismatch between the received fcs code and the computed crc residue will cause the pmon configurable accumulator #1 register to increment. receive frame check sequence errors are ignored when rfcse1en is set low. rabrt1en: the receive abort accumulate enable bit (rabrt1en) enables counting of receive hdlc abort events. when rabrt1en is set high, receipt of an abort code (at least 7 contiguous 1's) will cause the pm on configurable accumulator #1 register to increment. receive aborts are ignored when rabrt1en is set low. rlene1en: the receive packet length error accumulate enable bit (rlene1en) enables counting of receive packet length error events. when rlene1en is set high, receipt of a packet that is longer than the programmable maximum or of a packet that in not octet aligned w ill cause the pm on configurable accumulator #1 register to increment. (receipt of a packet that is both too long and not octet aligned results in only one increment.) receive packet length errors are ignored when rlene1en is set low. rp1en: the receive packet enable bit (rp1en) enables counting of receive error-free packets. when rp1en is set high, rece ipt of an error-free packet will cause the pmon configurable accumulator #1 register to increment. receive error- free packets are ignored when rp1en is set low. tabrt1en: the transmit abort accumulate enable bit (tabrt1en) enables counting of transmit hdlc abort events. when tabrt1en is set high, insertion of an abort in the outgoing stream will caus e the pmon config urable accumulator #1 register to increment. transmit aborts are ignored when tabrt1en is set low.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 116 tp1en: the transmit packet enable bit (tp1en) enables counting of transmit error-free packets. when tp1en is set high, transmission of an error-free packet will cause the pmon configurable accumulator #1 register to increment. transmit error-free packets are ignored when tp1en is set low. rspe2en: the receive small packet error accumulate enable bit (rspe2en) enables counting of minimum packet size violation events. when rspe2en is set high, receipt of a packet that is shor ter than 32 bits (crc-ccitt, unspecified crc or no crc) or 48 bits (crc-32) will cause the pmon configurable accumulator #2 register to increment. small packet errors are ignored when rspe2en is set low. rfcse2en: the receive frame check sequence error accumulate enable bit (rfcse2en) enables counting of receive fcs error events. when rfcse2en is set high, a mismatch between the received fcs code and the computed crc residue will cause the pmon configurable accumulator #2 register to increment. receive frame check sequence errors are ignored when rfcse2en is set low. rabrt2en: the receive abort accumulate enable bit (rabrt2en) enables counting of receive hdlc abort events. when rabrt2en is set high, receipt of an abort code (at least 7 contiguous 2's) will cause the pm on configurable accumulator #2 register to increment. receive aborts are ignored when rabrt2en is set low. rlene2en: the receive packet length error accumulate enable bit (rlene2en) enables counting of receive packet length error events. when rlene2en is set high, receipt of a packet that is longer than the programmable maximum or of a packet that in not octet aligned w ill cause the pm on configurable accumulator #2 register to increment. (receipt of a packet that is both too long and not octet aligned results in only one increment.) receive packet length errors are ignored when rlene2en is set low. rp2en: the receive packet enable bit (rp2en) enables counting of receive error-free packets. when rp2en is set high, rece ipt of an error-free packet will cause the pmon configurable accumulator #2 register to increment. receive error- free packets are ignored when rp2en is set low.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 117 tabrt2en: the transmit abort accumulate enable bit (tabrt2en) enables counting of transmit hdlc abort events. when tabrt2en is set high, insertion of an abort in the outgoing stream will cause the pmon configurable accumulator #2 register to increment. transmit aborts are ignored when tabrt2en is set low. tp2en: the transmit packet enable bit (tp2en) enables counting of transmit error-free packets. when tp2en is set high, transmission of an error-free packet will cause the pmon configurable accumulator #2 register to increment. transmit error-free packets are ignored when tp2en is set low.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 118 register 0x080 : gpic control bit type func tion default bit 31 to bit 14 unused xxxxxh bit 13 r/w rpwth[5] 0 bit 12 r/w rpwth[4] 0 bit 11 r/w rpwth[3] 0 bit 10 r/w rpwth[2] 0 bit 9 r/w rpwth[1] 0 bit 8 r/w rpwth[0] 0 bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 r/w pons_e 0 bit 2 r/w soe_e 0 bit 1 r/w lendian 1 bit 0 r/w reserved 0 this register configures the operation of the gpic. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. reserved: the reserved bit must be set low for correct operation of the freedm- 32p672.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 119 lendian: the little endian mode bit (lendian) selects between big endian or little endian format when reading packet data from and writing packet data to pci host memory. when lendian is set low, big endian format is selected. when lendian is set high, little endian format is selected. descriptor references and the contents of descriptors are always transferred in little endian format. please refer below for each format's byte ordering. table 14 ? big endian format 00 bit 31 24 23 16 15 8 7 bit 0 dword address 04 byte 0 byte 1 byte 2 byte 3 byte 4 byte 5 byte 6 byte 7 ? ? ? ? ? ? ? ? ? ? ? ? n-4 byte n-4 byte n-3 byte n-2 byte n-1 table 15 ? little endian format 00 bit 31 24 23 16 15 8 7 bit 0 dword address 04 byte 3 byte 2 byte 1 byte 0 byte 7 byte 6 byte 5 byte 4 ? ? ? ? ? ? ? ? ? ? ? ? n-4 byte n-1 byte n-2 byte n-3 byte n-4 soe_e: the stop on error enable (soe_e) bit determines the action the pci controller will take when a system or pa rity error occurs. when set high the pci controller will disconnect the pci re qb signal from the pci bus. this prevents the gpic from the becoming a master device on the pci bus in event of one of the following bits in the pci configuration command/status register being set: dpr, rtabt, mabt and serr. when the soe_e bit is set low the pci controller will continue to allow master transactions on the pci bus. setting this bit low after an error has occurred or clearing the appropriate bit the pc i configuration command/statu s register will reactivate the pci reqb signal and allow the gpic to resume servicing the local
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 120 masters. in the event of a system or parity error it is recommended that the core device be reset unless the cause of the fault can be determined. pons_e: the report perr on serr enable (pons_e) bit controls the source of system errors. when set high all parity errors will be signaled to the host via the serrb output signal. rpwth[5:0]: the receive packet write threshold bits (rpwth[5:0]) controls the amount of data in the write fifo before the gpic begins arbitrating for the bus. the gpic will begin requesting access to the pci bus when the number of dwords of packet data loaded by the rmac672 reaches the threshold specified by rpwth[5:0]. if the freedm-32p672 is being operated with pciclk at a higher frequency than sysclk, rpwth must be set to a value that ensures that the write fifo does not underflow due to data being read out of the fifo faster than data is written into the fifo. it is recommended that rpwth be set to a value not less than . pciclkfreq . freq sysclk rg . pciclkfreq . freq sysclk xfer 1 1 4 where rg is the minimum number of clock cycles in which gntb can be received after reqb has been asserted.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 121 register 0x100 : rcas indirect link and time-slot select bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r busy x bit 14 r/w rwb 0 bit 13 unused x bit 12 r/w reserved 0 bit 11 r/w reserved 0 bit 10 r/w link[4] 0 bit 9 r/w link[3] 0 bit 8 r/w link[2] 0 bit 7 r/w link[1] 0 bit 6 r/w link[0] 0 bit 5 unused x bit 4 r/w tslot[4] 0 bit 3 r/w tslot[3] 0 bit 2 r/w tslot[2] 0 bit 1 r/w tslot[1] 0 bit 0 r/w tslot[0] 0 this register provides the receive link and time-slot number used to access the channel provision ram. writing to this register triggers an indirect register access. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 122 tslot[4:0]: the indirect time-slot number bits (tsl ot[4:0]) indicate the time-slot to be configured or interrogated in the indirect access. for a channelised t1/j1 link, time-slots 1 to 24 are valid. for a channelised e1 link, time-slots 1 to 31 are valid. for an h-mvip link, time-slots 0 to 31 are valid. for unchannelised links, only time-slot 0 is valid. link[4:0]: the indirect link number bits (link[4:0]) select amongst the 32 receive links to be configured or interrogated in the indirect access. reserved: the reserved bits must be set low for correct operation of the freedm- 32p672 device. rwb: the indirect access control bit (rwb) selects between a configure (write) or interrogate (read) access to the channel provision ram. the address to the channel provision ram is constructed by concatenating the tslot[4:0] and link[4:0] bits. writing a logic zero to rwb triggers an indirect write operation. data to be written is taken from the prov, the cdlben and the chan[9:0] bits of the rcas indirect channel data register. writing a logic one to rwb triggers an indirect read operation. addressing of the ram is the same as in an indirect write operation. the data read can be found in the prov, the cdlben and the chan[9:0] bits of the rcas indirect channel data register. busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operation is available in the rcas indirect channel data register or to determine when a new indirect write operation may commence.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 123 register 0x104 : rcas indirect channel data bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w cdlben 0 bit 14 r/w prov 0 bit 13 to bit 10 unused xh bit 9 r/w chan[9] 0 bit 8 r/w chan[8] 0 bit 7 r/w chan[7] 0 bit 6 r/w chan[6] 0 bit 5 r/w chan[5] 0 bit 4 r/w chan[4] 0 bit 3 r/w chan[3] 0 bit 2 r/w chan[2] 0 bit 1 r/w chan[1] 0 bit 0 r/w chan[0] 0 this register contains the data read from the channel provision ram after an indirect read operation or the data to be inserted into the channel provision ram in an indirect write operation. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. chan[9:0]: the indirect data bits (chan[9:0]) report the channel number read from the channel provision ram after an indirect read operation has completed.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 124 channel number to be written to the channel provision ram in an indirect write operation must be set up in this register before triggering the write. chan[9:0] reflects the value written until the completion of a subsequent indirect read operation. prov: the indirect provision enable bit (prov) reports the channel provision enable flag read from the channel provision ram after an indirect read operation has completed. the provision enable flag to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. when prov is set high, the current receive data byte is processed as part of the channel as indicated by chan[9:0]. when prov is set low, the current time-slot does not belong to any channel and the receive data byte ignored. prov reflects the value written until the completion of a subsequent indirect read operation. cdlben: the indirect channel based diagnostic loopback enable bit (cdlben) reports the loopback enable flag read from channel provision ram after an indirect read operation has complete. the loopback enable flag to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. when cdlben is set high, the current receive data byte is to be over-written by data retrieved from the loopback fifo of the channel as indicated by chan[9:0]. when cdlben is set low, the current receive data byte is processed normally. cdlben reflects the value written until the completion of a subsequent indirect read operation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 125 register 0x108 : rcas framing bit threshold bit type func tion default bit 31 to bit 7 unused xxxxxxxh bit 6 r/w fthres[6] 0 bit 5 r/w fthres[5] 1 bit 4 r/w fthres[4] 0 bit 3 r/w fthres[3] 0 bit 2 r/w fthres[2] 1 bit 1 r/w fthres[1] 0 bit 0 r/w fthres[0] 1 this register contains the threshold used by the clock activity monitor to detect for framing bits/bytes. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. fthres[6:0]: the framing bit threshold bits (fthres[6:0]) contains the threshold used by the clock activity monitor to detect for the presence of framing bits. a counter in the clock activity monitor of each receive link increments on each rising edge of sysclk and is cleared, when the bsync bit of that link is set low, by each rising edge of the corresponding rclk[n]. when the bsync bit of that link is set high, the counter is cleared at every fourth rising edge of the corresponding rclk[n]. when the counter exceeds the threshold given by fthres[6:0], a framing bit/byte has been detected. fthres[6:0] should be set as a function of the sysclk period and the expected gapping width of rclk[n] during data bits and during framing bits/bytes. legal range of fthresh[6:0] is 'b0000001 to 'b 1111110.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 126 note: for operation with t1/j1 links and sysclk = 45 mhz, fthresh[6:0] should be set to ?b0100101?. the default value of this register reflects this mode of operation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 127 register 0x10c : rcas channel disable bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w chdis 0 bit 14 to bit 10 unused xxh bit 9 r/w dchan[9] 0 bit 8 r/w dchan[8] 0 bit 7 r/w dchan[7] 0 bit 6 r/w dchan[6] 0 bit 5 r/w dchan[5] 0 bit 4 r/w dchan[4] 0 bit 3 r/w dchan[3] 0 bit 2 r/w dchan[2] 0 bit 1 r/w dchan[1] 0 bit 0 r/w dchan[0] 0 this register controls the disabling of one specific channel to allow orderly provisioning of time-slots associated with that channel. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. dchan[9:0]: the disable channel number bits (dchan[9:0]) selects the channel to be disabled. when chdis is set high, t he channel specified by dchan[9:0] is disabled. data in time-slots associated with the specified channel is ignored. when chdis is set low, the channel specified by dchan[9:0] operates normally.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 128 chdis: the channel disable bit (chdis) controls the disabling of the channels specified by dchan[9:0]. when chdis is set high, the channel selected by dchan[9:0] is disabled. data in time-slots associated with the specified channel is ignored. when chdis is se t low, the channel specified by dchan[9:0] operates normally.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 129 register 0x180 ? 0x188 : rcas links #0 to #2 configuration bit type func tion default bit 31 to bit 5 unused xxxxxxxh bit 4 r/w bsync 0 bit 3 unused x bit 2 r/w mode[2] 0 bit 1 r/w mode[1] 0 bit 0 r/w mode[0] 0 this register configures operational modes of receive links #0 to #2. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. mode[2:0]: the mode select bits (mode[2:0]) configures the corresponding receive link. table 16 details this procedure. when link 4m (0 m 7) is configured for operation in 8.192 mbps h-mvip mode (mode[2:0]=?111?), data cannot be received on links 4m+1, 4m+2 and 4m+3. however, links 4m+1, 4m+2 and 4m+3 must be configured for 8.192 mbps h-mvip mode for correct operation of the rcas672. from a channel assignment point of view in the rcas672 (registers 0x100, 0x104), time-slots 0 through 31 of the h-mvip link are treated as time-slots 0 through 31 of link 4m, time-slots 32 through 63 of the h-mvip link are treated as time-slots 0 through 31 of link 4m+1, time-slots 64 through 95 of the h-mvip link are treated as time-slots 0 through 31 of link 4m+2 and time-slots 96 through 127 of the h-mvip link are treated as time- slots 0 through 31 of link 4m+3.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 130 table 16 - receive links #0 to #2 configuration mode[2:0] link configuration 000 unchannelised 001 channelised t1/j1 (24 time slots labeled 1-24) 010 channelised e1 (31 time slots labeled 1-31) 011 2 mbps h-mvip (32 time slots labeled 0-31) 100 reserved 101 reserved 110 reserved 111 8 mbps h-mvip (128 time slots mapped to time- slots 0 through 31 of links 4m, 4m+1, 4m+2 and 4m+3) bsync: the byte synchronization enable bit (bsync) controls the interpretation of gaps in rclk[n] when link #n is in unchannelised mode (mode[2:0]=?000?). when bsync is set high, the data bit on rd[n] clocked in by the first rising edge of rclk[n] after an extended quiescent period is considered to be the most significant bit of a data byte. when bsync is set low, gaps in rclk[n] carry no special significance. bsync is ignored when mode[2:0] ?000?.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 131 register 0x18c ? 0x1fc : rcas links #3 to #31 configuration bit type func tion default bit 31 to bit 3 unused xxxxxxxxh bit 2 r/w mode[2] 0 bit 1 r/w mode[1] 0 bit 0 r/w mode[0] 0 this register configures operational modes of receive links #3 to #31. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. mode[2:0]: the mode select bits (mode[2:0]) configures the corresponding receive link. table 17 details this procedure. when link 4m (0 m 7) is configured for operation in 8.192 mbps h-mvip mode (mode[2:0]=?111?), data cannot be received on links 4m+1, 4m+2 and 4m+3. however, links 4m+1, 4m+2 and 4m+3 must be configured for 8.192 mbps h-mvip mode for correct operation of the rcas672. from a channel assignment point of view in the rcas672 (registers 0x100, 0x104), time-slots 0 through 31 of the h-mvip link are treated as time-slots 0 through 31 of link 4m, time-slots 32 through 63 of the h-mvip link are treated as time-slots 0 through 31 of link 4m+1, time-slots 64 through 95 of the h-mvip link are treated as time-slots 0 through 31 of link 4m+2 and time-slots 96 through 127 of the h-mvip link are treated as time- slots 0 through 31 of link 4m+3.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 132 table 17 - receive links #3 to #31 configuration mode[2:0] link configuration 000 unchannelised 001 channelised t1/j1 (24 time slots labeled 1-24) 010 channelised e1 (31 time slots labeled 1-31) 011 2 mbps h-mvip (32 time slots labeled 0-31) 100 reserved 101 reserved 110 reserved 111 8 mbps h-mvip (128 time slots mapped to time- slots 0 through 31 of links 4m, 4m+1, 4m+2 and 4m+3)
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 133 register 0x200 : rhdl indirect channel select bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r busy x bit 14 r/w crwb 0 bit 13 to bit 10 unused xh bit 9 r/w chan[9] 0 bit 8 r/w chan[8] 0 bit 7 r/w chan[7] 0 bit 6 r/w chan[6] 0 bit 5 r/w chan[5] 0 bit 4 r/w chan[4] 0 bit 3 r/w chan[3] 0 bit 2 r/w chan[2] 0 bit 1 r/w chan[1] 0 bit 0 r/w chan[0] 0 this register provides the channel number used to access the receive channel provision ram. writing to this register triggers an indirect channel register access. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. chan[9:0]: the indirect channel number bits (chan[9:0]) indicate the receive channel to be configured or interrogated in the indirect access.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 134 crwb: the channel indirect access control bit (crwb) selects between a configure (write) or interrogate (read) access to the receive channel provision ram. writing a logic zero to crwb triggers an indirect write operation. data to be written is taken from the indirect channel data registers. writing a logic one to crwb triggers an indirect read operation. the data read can be found in the indirect channel data registers. busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operati on is available in the rhdl indirect channel data #1 and #2 registers or to determine when a new indirect write operation may commence.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 135 register 0x204 : rhdl indirect channel data register #1 bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w prov 0 bit 14 r/w strip 0 bit 13 r/w delin 0 bit 12 r tavail x bit 11 w reserved x bit 10 w fptr[10] x bit 9 w fptr[9] x bit 8 w fptr[8] x bit 7 w fptr[7] x bit 6 w fptr[6] x bit 5 w fptr[5] x bit 4 w fptr[4] x bit 3 w fptr[3] x bit 2 w fptr[2] x bit 1 w fptr[1] x bit 0 w fptr[0] x this register contains data read from the channel provision ram after an indirect read operation or data to be inserted into the channel provision ram in an indirect write operation. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 136 fptr[10:0]: the indirect fifo block pointer (fptr[10:0]) identifies one of the blocks of the circular linked list in the partial packet buffer used in the logical fifo of the current channel. the fifo pointer to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. the fifo point er value can be any one of the blocks provisioned to form the circular buffer. reserved: the reserved bit must be set low for correct operation of the freedm- 32p672 device. tavail: the indirect transac tion available bit (tavail) r eports the fill level of the partial packet buffer used in the logical fifo of the current channel. tavail is set high when the fifo of the current channel contains sufficient data, as controlled by xfer[3:0], to request a dma transfer to the host memory. tavail is set low when the amount of receive data is too small to require a transfer to host memory. tavail is updated by an indirect channel read operation. delin: the indirect delineate enable bit (delin) configures the hdlc processor to perform flag sequence delineation and bit de-stuffing on the incoming data stream. the delineate enable bit to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when delin is set high, flag sequence delineation and bit de-stuffing is performed on the incoming data stream. when delin is set low, the hdlc processor does not perform any processing (flag sequence delineation, bit de-stuffing nor crc veri fication) on the incoming stream. delin reflects the value written until the completion of a subsequent indirect channel read operation. strip: the indirect frame check sequence discard bit (strip) configures the hdlc processor to remove the crc from the incoming frame when writing the data to the channel fifo. the fcs discard bit to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when strip is set high and crc[1:0] is not equal to "00", the received crc value is not written to the fifo. when strip is set low, the received crc value is written to the fifo. the bytes in buffer field of the rpd correctly reflect the presence/absence of crc bytes in the buffer. the value of strip is ignored when delin is low. strip reflects
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 137 the value written until the completion of a subsequent indirect channel read operation. prov: the indirect provision enable bit (prov) reports the channel provision enable flag read from the channel provision ram after an indirect channel read operation has completed. the provision enable flag to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. when prov is set high, the hdlc processor will process data on the c hannel specified by chan[9:0]. when prov is set low, the hdlc proce ssor will ignore data on the channel specified by chan[9:0]. prov reflects the value written until the completion of a subsequent indirect channel read operation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 138 register 0x208 : rhdl indirect channel data register #2 bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w 7bit 0 bit 14 r/w priority 0 bit 13 r/w invert 0 bit 12 unused x bit 11 r/w crc[1] 0 bit 10 r/w crc[0] 0 bit 9 r/w offset[1] 0 bit 8 r/w offset[0] 0 bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 r/w xfer[3] 0 bit 2 r/w xfer[2] 0 bit 1 r/w xfer[1] 0 bit 0 r/w xfer[0] 0 this register contains data read from the channel provision ram after an indirect read operation or data to be inserted into the channel provision ram in an indirect write operation. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 139 xfer[3:0]: the indirect channel transfer size (xfer[3:0]) configures the amount of data transferred in each transaction. the channel transfer size to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. when the channel fifo depth reaches the depth specified by xfer[3:0] or when an end-of-packet exists in the fifo, a request will be made to the rmac672 to initiate a pci write access to transfer the data to the pci host. channel transfer size is measured in 16 byte blocks. the amount of data transferred and the dept h threshold are specified by given setting is: xfer[3:0] + 1 blocks = 16 * (xfer[3:0] + 1) bytes xfer[3:0] should be set such that t he number of blocks transferred is at least two fewer than the total allocated to the associated channel. xfer[3:0] reflects the value written until the completion of a subsequent indirect channel read operation. offset[1:0]: the packet byte offset (offset[1:0]) configures the partial packet processor to insert invalid bytes at the beginning of a packet stored in the channel fifo. the value of offset[1:0] to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. the number of bytes inserted before the beginning of a hdlc packet is defined by the binary value of offset[1:0]. offset[1:0] reflects the value written until the completion of a subsequent indirect channel read operation. crc[1:0]: the crc algorithm bits (crc[1:0]) configures the hdlc processor to perform crc verification on the incoming data stream. the value of crc[1:0] to be written to the channel pr ovision ram, in an indirect channel write operation, must be set up in this register before triggering the write. crc[1:0] is ignored when delin is low. crc[1:0] reflects the value written until the completion of a subsequent indirect channel read operation. table 18 ? crc[1:0] settings crc[1] crc[0] operation 0 0 no verification 0 1 crc-ccitt 1 0 crc-32
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 140 crc[1] crc[0] operation 1 1 reserved invert: the hdlc data inversion bit (invert) configures the hdlc processor to logically invert the incoming hdlc stream from the rcas672 before processing it. the value of invert to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when invert is set to one, the hdlc stream is logically inverted before processing. when invert is set to zero, the hdlc stream is not inverted before processing. invert reflects the value written until the completion of a subsequent indirect channel read operation. priority: the channel fifo priority bit (priority) informs the partial packet processor that the channel has prec edence over other channels when being serviced by the rmac672 block for transfer to the pci host. the value of priority to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. channel fifos with priority set to one are serviced by the rmac672 before channel fifos with priority set to zero. channels with an hdlc data rate to fifo size ratio that is significantly higher than other channels should have priority set to one. priority reflects the value written until the completion of a subsequent indirect channel read operation. 7bit: the 7bit enable bit (7bit) configures the hdlc processor to ignore the least significant bit of each octet in the corresponding link rd[n]. the value of 7bit to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when 7bit is set high, the least significant bit (last bit of each octet received), is ignored. when 7bit is set low, the entire receive data stream is processed. 7bit reflects the value written until the completion of a subsequent indirect channel read operation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 141 register 0x210 : rhdl indirect block select bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r busy x bit 14 r/w brwb x bit 13 unused x bit 12 unused x bit 11 unused x bit 10 r/w block[10] x bit 9 r/w block[9] x bit 8 r/w block[8] x bit 7 r/w block[7] x bit 6 r/w block[6] x bit 5 r/w block[5] x bit 4 r/w block[4] x bit 3 r/w block[3] x bit 2 r/w block[2] x bit 1 r/w block[1] x bit 0 r/w block[0] x this register provides the block number used to access the block pointer ram. writing to this register triggers an indirect block register access. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 142 block[10:0]: the indirect block number (block[10:0]) indicate the block to be configured or interrogated in the indirect access. reserved: the reserved bit must be set low for correct operation of the freedm- 32p672 device. brwb: the block indirect access control bit (brwb) selects between a configure (write) or interrogate (read) access to the block pointer ram. writing a logic zero to brwb triggers an indirect block write operation. data to be written is taken from the indirect block data register. writing a logic one to brwb triggers an indirect block read operation. the data read can be found in the indirect block data register. busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operat ion is available in the rhdl indi rect block data register or to determine when a new indirect write operation may commence.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 143 register 0x214 : rhdl indirect block data bit type func tion default bit 31 to bit 12 unused xxxxxh bit 11 r/w reserved x bit 10 r/w bptr[10] 0 bit 9 r/w bptr[9] 0 bit 8 r/w bptr[8] 0 bit 7 r/w bptr[7] 0 bit 6 r/w bptr[6] 0 bit 5 r/w bptr[5] 0 bit 4 r/w bptr[4] 0 bit 3 r/w bptr[3] 0 bit 2 r/w bptr[2] 0 bit 1 r/w bptr[1] 0 bit 0 r/w bptr[0] 0 this register contains data read from the block pointer ram after an indirect block read operation or data to be inserted into the block pointer ram in an indirect block write operation. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. bptr[10:0]: the indirect block pointer (bptr[10:0]) configures the block pointer of the block specified by the indirect block select register. the block pointer to be written to the block pointer ram, in an indirect write operation, must be set up in this register before triggering the write. the block pointer value is the block number of the next block in the linked lis t. a circular list of blocks must be formed in order to use the block list as a receive channel fifo buffer.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 144 bptr[10:0] reflects the value written until the completion of a subsequent indirect block read operation. when provisioning a channel fifo, all block pointers must be re-written to properly initialize the fifo. reserved: the reserved bit must be set low for correct operation of the freedm- 32p672 device.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 145 register 0x220 : rhdl configuration bit type func tion default bit 31 to bit 10 unused xxxxxxh bit 9 r/w lenchk 0 bit 8 r/w tstd 0 bit 7 unused x bit 6 unused x bit 5 unused x bit 4 unused x bit 3 unused x bit 2 unused x bit 1 unused x bit 0 unused x this register configures all provisioned receive channels. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. tstd: the telecom standard bit (tstd) controls the bit ordering of the hdlc data transferred to the pci host. when tstd is set low, the least significant bit of the each byte on the pci bus (ad[0], ad[8], ad[16] and ad[24]) is the first hdlc bit received and the most significant bit of each byte (ad[7], ad[15], ad[23] and ad[31]) is the last hdlc bit received (datacom standard). when tstd is set high, ad[0], ad[8], ad[16] and ad[24] are the last hdlc bit received and ad[7], ad[15], ad[23] and ad[31] are the first hdlc bit received (telecom standard).
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 146 lenchk: the packet length error check bit (lenchk) controls the checking of receive packets that are longer than the maximum programmed length. when lenchk is set high, receive packets are aborted and the re mainder of the frame discarded when the packet exceeds the maximum packet length given by max[15:0]. when lenchk is set low, receive packets are not checked for maximum size and max[15:0] must be set to 'hffff.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 147 register 0x224 : rhdl maximum packet length bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w max[15] 1 bit 14 r/w max[14] 1 bit 13 r/w max[13] 1 bit 12 r/w max[12] 1 bit 11 r/w max[11] 1 bit 10 r/w max[10] 1 bit 9 r/w max[9] 1 bit 8 r/w max[8] 1 bit 7 r/w max[7] 1 bit 6 r/w max[6] 1 bit 5 r/w max[5] 1 bit 4 r/w max[4] 1 bit 3 r/w max[3] 1 bit 2 r/w max[2] 1 bit 1 r/w max[1] 1 bit 0 r/w max[0] 1 this register configures the maximum legal hdlc packet byte length. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. max[15:0]: the maximum hdlc packet length (max[15:0]) configures the freedm- 32p672 to reject hdlc packets longer than a maximum size when lenchk
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 148 is set high. receive packets with total length, including address, control, information and fcs fields, greater than max[15:0] bytes are aborted. when lenchk is set low, aborts are not g enerated regardless of packet length and max[15:0] must be set to 'hffff.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 149 register 0x280 : rmac control bit type func tion default bit 31 to bit 13 unused xxxxxh bit 12 r/w reserved 0 bit 11 r/w rpq_sfn[1] 0 bit 10 r/w rpq_sfn[0] 0 bit 9 r/w rpq_lfn[1] 0 bit 8 r/w rpq_lfn[0] 0 bit 7 r/w rpq_rdyn[2] 0 bit 6 r/w rpq_rdyn[1] 0 bit 5 r/w rpq_rdyn[0] 0 bit 4 r/w rawmax[1] 1 bit 3 r/w rawmax[0] 1 bit 2 r/w scache 1 bit 1 r/w lcache 1 bit 0 r/w enable 0 this register configures the rmac672 block. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. enable: the enable bit determines whether or not the rmac672 accepts data from the rhdl672 block and sends it to host memory. when set to 1, these tasks are enabled. when set to 0, they are disabled.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 150 lcache: the large buffer cache enable bit (lcache) enables caching of large buffer rpdrs. when lcache is set high, rpdrs are fetched from the rpdr large buffer free queue in groups of up to six. when lcache is set low, rpdrs are fetched one at a time. scache: the small buffer cache enable bit (scache) enables caching of small buffer rpdrs. when scache is set high, rpdrs are fetched from the rpdr small buffer free queue in groups of up to six. when scache is set low, rpdrs are fetched one at a time. rawmax[1:0]: the rawmax[1:0] field determines how ?raw? (i.e. non packet delimited) data is written to host memory. raw data is written to buffers in host memory in the same manner as packet delimited data. whenever rawmax[1:0] + 1 buffers have been filled, the resulting buffer chain is placed in the ready queue. rpq_rdyn[2:0]: the rpq_rdyn[2:0] field sets the number of receive packet descriptor references (rpdrs) that must be placed onto the rpdr ready queue before the rpdr ready interrupt (rpqrdyi) is asserted, as follows: table 19 ? rpq_rdyn[2:0] settings rpq_rdyn[2:0] no of rpdrs 000 1 001 4 010 6 011 8 100 16 101 32 110 reserved 111 reserved if the value of rpq_rdyn[2:0] is altered, the new value does not become effective until after the rpqrdyi interrupt is next generated.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 151 rpq_lfn[1:0]: the rpq_lfn[1:0] field sets the number of times that a block of rpdrs are read from the large buffer free queue to the rmac672s internal cache before the rpdr large buffer free queue interrupt (rpqlfi) is asserted, as follows: table 20 ? rpq_lfn[1:0] settings rpq_lfn[1:0] no of reads 00 1 01 4 10 8 11 reserved if the value of rpq_lfn[1:0] is altered, the new value does not become effective until after the rpqlfi interrupt is next generated. rpq_sfn[1:0]: the rpq_sfn[1:0] field sets the number of times that a block of rpdrs are read from the small buffer free queue to the rmac672s internal cache before the rpdr small buffer free queue interrupt (rpqsfi) is asserted, as follows: table 21 ? rpq_sfn[1:0] settings rpq_sfn[1:0] no of reads 00 1 01 4 10 8 11 reserved if the value of rpq_sfn[1:0] is altered, the new value does not become effective until after the rpqsfi interrupt is next generated. reserved: the reserved bit must be set low for correct operation of the freedm- 32p672 device.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 152 register 0x284 : rmac indirect channel provisioning bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r busy x bit 14 r/w rwb 0 bit 13 to bit 11 unused xh bit 10 r/w prov 0 bit 9 r/w chan[9] 0 bit 8 r/w chan[8] 0 bit 7 r/w chan[7] 0 bit 6 r/w chan[6] 0 bit 5 r/w chan[5] 0 bit 4 r/w chan[4] 0 bit 3 r/w chan[3] 0 bit 2 r/w chan[2] 0 bit 1 r/w chan[1] 0 bit 0 r/w chan[0] 0 the channel provisioning register is used to temporarily unprovision channels, and also to query the provision status of channels. channel is permanently provisioned and can only be unprovisioned transiently. when a channel is unprovisioned, a partially received packet, if any, will be flushed and marked as unprovisioned in the rpdrr queue status fi eld. the channel then returns to being provisioned automatically. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 153 chan[9:0]: the indirect data bits (chan[9:0]) report the channel number read from the rmac672 internal memory after an indirect read operation has completed. channel number to be written to the rmac672 internal memory in an indirect write operation must be set up in this register before triggering the write. chan[9:0] reflects the value written until the completion of a subsequent indirect read operation. prov: the indirect provision enable bit (prov) reports the channel provision enable flag read from the rmac672 internal memory after an indirect read operation has completed. the provision enable flag to be written to the rmac672 internal memory, in an indirect write operation, must be set up in this register before triggering the write. when prov is set high, the channel indicated by chan[9:0] is provisioned. when prov is set low, the channel indicated by chan[9:0] is unprovisioned temporarily. any partially received packets are flushed and the status in the rpdrr queue is marked unprovisioned. the channel then returns to being provisi oned and prov will report a logic high after the next indirect read operation. prov reflects the value written until the completion of a subsequent indirect read operation. rwb: the read/write bar (rwb) bit selects between a provisioning/unprovisioning operation (write) or a query operation (read). writing a logic 0 to rwb triggers the provisioning or unprovisioning of a channel as specified by chan[9:0] and prov. writing a logic 1 to rwb triggers a query of the channel specified by chan[9:0]. busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operation is available or to determine when a new indirect write operation may commence.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 154 register 0x288 : rmac packet descriptor table base lsw bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdtb[15] 0 bit 14 r/w rpdtb[14] 0 bit 13 r/w rpdtb[13] 0 bit 12 r/w rpdtb[12] 0 bit 11 r/w rpdtb[11] 0 bit 10 r/w rpdtb[10] 0 bit 9 r/w rpdtb[9] 0 bit 8 r/w rpdtb[8] 0 bit 7 r/w rpdtb[7] 0 bit 6 r/w rpdtb[6] 0 bit 5 r/w rpdtb[5] 0 bit 4 r/w rpdtb[4] 0 bit 3 r/w rpdtb[3] 0 bit 2 r/w rpdtb[2] 0 bit 1 r/w rpdtb[1] 0 bit 0 r/w rpdtb[0] 0 this register provides the less significant word of the receive descriptor table base address. the contents of this register is held in a holding register until a write access to the companion rmac receive descriptor table base msw register. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 155 register 0x28c : rmac packet descriptor table base msw bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdtb[31] 0 bit 14 r/w rpdtb[30] 0 bit 13 r/w rpdtb[29] 0 bit 12 r/w rpdtb[28] 0 bit 11 r/w rpdtb[27] 0 bit 10 r/w rpdtb[26] 0 bit 9 r/w rpdtb[25] 0 bit 8 r/w rpdtb[24] 0 bit 7 r/w rpdtb[23] 0 bit 6 r/w rpdtb[22] 0 bit 5 r/w rpdtb[21] 0 bit 4 r/w rpdtb[20] 0 bit 3 r/w rpdtb[19] 0 bit 2 r/w rpdtb[18] 0 bit 1 r/w rpdtb[17] 0 bit 0 r/w rpdtb[16] 0 this register provides the more significant word of the receive descriptor table base address. the contents of the companion rmac receive descriptor table base lsw register is held in a holding register until a write access to this register, at which point, the base address of the receive packet descriptor table is updated. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 156 rpdtb[31:0]: the receive packet descriptor table base bits (rpdtb[31:0]) provides the base address of the receive packet descriptor table in pci host memory. this register is initialised by the host. to calculate the physical address of a rpd, the 15 bit rpd offset must be added to bits 31 to 4 of the receive packet descriptor table base (rpdtb[31:4]). the table must be on a 16 byte boundary and thus the least significant four bits must be written to logic zero.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 157 register 0x290 : rmac queue base lsw bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rqb[15] 0 bit 14 r/w rqb[14] 0 bit 13 r/w rqb[13] 0 bit 12 r/w rqb[12] 0 bit 11 r/w rqb[11] 0 bit 10 r/w rqb[10] 0 bit 9 r/w rqb[9] 0 bit 8 r/w rqb[8] 0 bit 7 r/w rqb[7] 0 bit 6 r/w rqb[6] 0 bit 5 r/w rqb[5] 0 bit 4 r/w rqb[4] 0 bit 3 r/w rqb[3] 0 bit 2 r/w rqb[2] 0 bit 1 r/w rqb[1] 0 bit 0 r/w rqb[0] 0 this register provides the less significant word of the receive queue base address. the contents of this register is held in a holding register until a write access to the companion rmac receive queue base msw register. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 158 register 0x294 : rmac queue base msw bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rqb[31] 0 bit 14 r/w rqb[30] 0 bit 13 r/w rqb[29] 0 bit 12 r/w rqb[28] 0 bit 11 r/w rqb[27] 0 bit 10 r/w rqb[26] 0 bit 9 r/w rqb[25] 0 bit 8 r/w rqb[24] 0 bit 7 r/w rqb[23] 0 bit 6 r/w rqb[22] 0 bit 5 r/w rqb[21] 0 bit 4 r/w rqb[20] 0 bit 3 r/w rqb[19] 0 bit 2 r/w rqb[18] 0 bit 1 r/w rqb[17] 0 bit 0 r/w rqb[16] 0 this register provides the more significant word of the receive queue base address. the contents of the companion rmac receive queue base lsw register is held in a holding register until a write access to this register, at which point, the base address of the receive queue is updated. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 159 rqb[31:0]: the receive queue base bits (rqb[31:0]) provides the base address of the large buffer rpdr free, small buffer rpdr free and rpdr ready queues in pci host memory. this register is initialised by the host. to calculate the physical address of a particular receive queue element, the rqb bits are added with the appropriate queue start, end, read or write index registers to form the physical address. the base address must be dword aligned and thus the least significant two bits must be written to logic zero.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 160 register 0x298 : rmac packet descriptor reference large buffer free queue start bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdrlfqs[15] 0 bit 14 r/w rpdrlfqs[14] 0 bit 13 r/w rpdrlfqs[13] 0 bit 12 r/w rpdrlfqs[12] 0 bit 11 r/w rpdrlfqs[11] 0 bit 10 r/w rpdrlfqs[10] 0 bit 9 r/w rpdrlfqs[9] 0 bit 8 r/w rpdrlfqs[8] 0 bit 7 r/w rpdrlfqs[7] 0 bit 6 r/w rpdrlfqs[6] 0 bit 5 r/w rpdrlfqs[5] 0 bit 4 r/w rpdrlfqs[4] 0 bit 3 r/w rpdrlfqs[3] 0 bit 2 r/w rpdrlfqs[2] 0 bit 1 r/w rpdrlfqs[1] 0 bit 0 r/w rpdrlfqs[0] 0 this register provides the packet descriptor reference large buffer free queue start address. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 161 rpdrlfqs[15:0]: the receive packet descriptor reference (rpdr) large buffer free queue start bits (rpdrlfqs[15:0]) define bits 17 to 2 of the receive packet descriptor reference large buffer free queue start address. this register is initialised by the host. the physical start address of the rpdrlf queue is the sum of rpdrlfqs[15:0] left shifted by 2 bits with the rqb[31:0] bits in the rmac receive queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 162 register 0x29c : rmac packet descriptor reference large buffer free queue write bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdrlfqw[15] 0 bit 14 r/w rpdrlfqw[14] 0 bit 13 r/w rpdrlfqw[13] 0 bit 12 r/w rpdrlfqw[12] 0 bit 11 r/w rpdrlfqw[11] 0 bit 10 r/w rpdrlfqw[10] 0 bit 9 r/w rpdrlfqw[9] 0 bit 8 r/w rpdrlfqw[8] 0 bit 7 r/w rpdrlfqw[7] 0 bit 6 r/w rpdrlfqw[6] 0 bit 5 r/w rpdrlfqw[5] 0 bit 4 r/w rpdrlfqw[4] 0 bit 3 r/w rpdrlfqw[3] 0 bit 2 r/w rpdrlfqw[2] 0 bit 1 r/w rpdrlfqw[1] 0 bit 0 r/w rpdrlfqw[0] 0 this register provides the packet descriptor reference large buffer free queue write address. notes 1. this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 163 2. if consecutive write accesses to this register are performed, they must be spaced at least 4 sysclk periods apart. rpdrlfqw[15:0]: the receive packet descriptor reference (rpdr) large buffer free queue write bits (rpdrlfqw[15:0]) define bits 17 to 2 of the receive packet descriptor reference large buffer free queue write pointer. this register is initialised by the host. the physical write address in the rpdrlf queue is the sum of rpdrlfqw[15:0] left shifted by 2 bits with the rqb[31:0] bits in the rmac receive queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 164 register 0x2a0 : rmac packet descriptor reference large buffer free queue read bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdrlfqr[15] 0 bit 14 r/w rpdrlfqr[14] 0 bit 13 r/w rpdrlfqr[13] 0 bit 12 r/w rpdrlfqr[12] 0 bit 11 r/w rpdrlfqr[11] 0 bit 10 r/w rpdrlfqr[10] 0 bit 9 r/w rpdrlfqr[9] 0 bit 8 r/w rpdrlfqr[8] 0 bit 7 r/w rpdrlfqr[7] 0 bit 6 r/w rpdrlfqr[6] 0 bit 5 r/w rpdrlfqr[5] 0 bit 4 r/w rpdrlfqr[4] 0 bit 3 r/w rpdrlfqr[3] 0 bit 2 r/w rpdrlfqr[2] 0 bit 1 r/w rpdrlfqr[1] 0 bit 0 r/w rpdrlfqr[0] 0 this register provides the packet descriptor reference large buffer free queue read address. notes 1. this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 165 2. if consecutive write accesses to this register are performed, they must be spaced at least 4 sysclk periods apart. rpdrlfqr[15:0]: the receive packet descriptor reference (rpdr) large buffer free queue read bits (rpdrlfqr[15:0]) define bits 17 to 2 of the receive packet descriptor reference large buffer free queue read pointer. this register is initialised by the host. the physical read address in the rpdrlf queue is the sum of rpdrlfqr[15:0] left shifted by 2 bits with the rqb[31:0] bits in the rmac receive queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 166 register 0x2a4 : rmac packet descriptor reference large buffer free queue end bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdrlfqe[15] 0 bit 14 r/w rpdrlfqe[14] 0 bit 13 r/w rpdrlfqe[13] 0 bit 12 r/w rpdrlfqe[12] 0 bit 11 r/w rpdrlfqe[11] 0 bit 10 r/w rpdrlfqe[10] 0 bit 9 r/w rpdrlfqe[9] 0 bit 8 r/w rpdrlfqe[8] 0 bit 7 r/w rpdrlfqe[7] 0 bit 6 r/w rpdrlfqe[6] 0 bit 5 r/w rpdrlfqe[5] 0 bit 4 r/w rpdrlfqe[4] 0 bit 3 r/w rpdrlfqe[3] 0 bit 2 r/w rpdrlfqe[2] 0 bit 1 r/w rpdrlfqe[1] 0 bit 0 r/w rpdrlfqe[0] 0 this register provides the packet descriptor reference large buffer free queue end address. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 167 rpdrlfqe[15:0]: the receive packet descriptor reference (rpdr) large buffer free queue end bits (rpdrlfqe[15:0]) define bits 17 to 2 of the receive packet descriptor reference large buffer free queue end address. this register is initialised by the host. the physical end address in the rpdrlf queue is the sum of rpdrlfqe[15:0] left shifted by 2 bits with the rqb[31:0] bits in the rmac receive queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 168 register 0x2a8 : rmac packet descriptor reference small buffer free queue start bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdrsfqs[15] 0 bit 14 r/w rpdrsfqs[14] 0 bit 13 r/w rpdrsfqs[13] 0 bit 12 r/w rpdrsfqs[12] 0 bit 11 r/w rpdrsfqs[11] 0 bit 10 r/w rpdrsfqs[10] 0 bit 9 r/w rpdrsfqs[9] 0 bit 8 r/w rpdrsfqs[8] 0 bit 7 r/w rpdrsfqs[7] 0 bit 6 r/w rpdrsfqs[6] 0 bit 5 r/w rpdrsfqs[5] 0 bit 4 r/w rpdrsfqs[4] 0 bit 3 r/w rpdrsfqs[3] 0 bit 2 r/w rpdrsfqs[2] 0 bit 1 r/w rpdrsfqs[1] 0 bit 0 r/w rpdrsfqs[0] 0 this register provides the packet descriptor reference small buffer free queue start address. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 169 rpdrsfqs[15:0]: the receive packet descriptor reference (rpdr) small buffer free queue start bits (rpdrsfqs[15:0]) define bits 17 to 2 of the receive packet descriptor reference small buffer free queue start address. this register is initialised by the host. the physical start address of the rpdrsf queue is the sum of rpdrsfqs[15:0] left shifted by 2 bits with the rqb[31:0] bits in the rmac receive queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 170 register 0x2ac : rmac packet descriptor reference small buffer free queue write bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdrsfqw[15] 0 bit 14 r/w rpdrsfqw[14] 0 bit 13 r/w rpdrsfqw[13] 0 bit 12 r/w rpdrsfqw[12] 0 bit 11 r/w rpdrsfqw[11] 0 bit 10 r/w rpdrsfqw[10] 0 bit 9 r/w rpdrsfqw[9] 0 bit 8 r/w rpdrsfqw[8] 0 bit 7 r/w rpdrsfqw[7] 0 bit 6 r/w rpdrsfqw[6] 0 bit 5 r/w rpdrsfqw[5] 0 bit 4 r/w rpdrsfqw[4] 0 bit 3 r/w rpdrsfqw[3] 0 bit 2 r/w rpdrsfqw[2] 0 bit 1 r/w rpdrsfqw[1] 0 bit 0 r/w rpdrsfqw[0] 0 this register provides the packet descriptor reference small buffer free queue write address. notes 1. this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 171 2. if consecutive write accesses to this register are performed, they must be spaced at least 4 sysclk periods apart. rpdrsfqw[15:0]: the receive packet descriptor reference (rpdr) small buffer free queue write bits (rpdrsfqw[15:0]) define bits 17 to 2 of the receive packet descriptor reference small buffer free queue write pointer. this register is initialised by the host. the physical write address in the rpdrsf queue is the sum of rpdrsfqw[15:0] left shifted by 2 bits with the rqb[31:0] bits in the rmac receive queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 172 register 0x2b0 : rmac packet descriptor reference small buffer free queue read bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdrsfqr[15] 0 bit 14 r/w rpdrsfqr[14] 0 bit 13 r/w rpdrsfqr[13] 0 bit 12 r/w rpdrsfqr[12] 0 bit 11 r/w rpdrsfqr[11] 0 bit 10 r/w rpdrsfqr[10] 0 bit 9 r/w rpdrsfqr[9] 0 bit 8 r/w rpdrsfqr[8] 0 bit 7 r/w rpdrsfqr[7] 0 bit 6 r/w rpdrsfqr[6] 0 bit 5 r/w rpdrsfqr[5] 0 bit 4 r/w rpdrsfqr[4] 0 bit 3 r/w rpdrsfqr[3] 0 bit 2 r/w rpdrsfqr[2] 0 bit 1 r/w rpdrsfqr[1] 0 bit 0 r/w rpdrsfqr[0] 0 this register provides the packet descriptor reference small buffer free queue read address. notes 1. this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 173 2. if consecutive write accesses to this register are performed, they must be spaced at least 4 sysclk periods apart. rpdrsfqr[15:0]: the receive packet descriptor reference (rpdr) small buffer free queue read bits (rpdrsfqr[15:0]) define bits 17 to 2 of the receive packet descriptor reference small buffer free queue read pointer. this register is initialised by the host. the physical read address in the rpdrsf queue is the sum of rpdrsfqr[15:0] left shifted by 2 bits with the rqb[31:0] bits in the rmac receive queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 174 register 0x2b4 : rmac packet descriptor reference small buffer free queue end bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdrsfqe[15] 0 bit 14 r/w rpdrsfqe[14] 0 bit 13 r/w rpdrsfqe[13] 0 bit 12 r/w rpdrsfqe[12] 0 bit 11 r/w rpdrsfqe[11] 0 bit 10 r/w rpdrsfqe[10] 0 bit 9 r/w rpdrsfqe[9] 0 bit 8 r/w rpdrsfqe[8] 0 bit 7 r/w rpdrsfqe[7] 0 bit 6 r/w rpdrsfqe[6] 0 bit 5 r/w rpdrsfqe[5] 0 bit 4 r/w rpdrsfqe[4] 0 bit 3 r/w rpdrsfqe[3] 0 bit 2 r/w rpdrsfqe[2] 0 bit 1 r/w rpdrsfqe[1] 0 bit 0 r/w rpdrsfqe[0] 0 this register provides the packet descriptor reference small buffer free queue end address. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 175 rpdrsfqe[15:0]: the receive packet descriptor reference (rpdr) small buffer free queue end bits (rpdrsfqe[15:0]) define bits 17 to 2 of the receive packet descriptor reference small buffer free queue end address. this register is initialised by the host. the physical end address in the rpdrsf queue is the sum of rpdrsfqe[15:0] left shifted by 2 bits with the rqb[31:0] bits in the rmac receive queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 176 register 0x2b8 : rmac packet descrip tor reference ready queue start bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdrrqs[15] 0 bit 14 r/w rpdrrqs[14] 0 bit 13 r/w rpdrrqs[13] 0 bit 12 r/w rpdrrqs[12] 0 bit 11 r/w rpdrrqs[11] 0 bit 10 r/w rpdrrqs[10] 0 bit 9 r/w rpdrrqs[9] 0 bit 8 r/w rpdrrqs[8] 0 bit 7 r/w rpdrrqs[7] 0 bit 6 r/w rpdrrqs[6] 0 bit 5 r/w rpdrrqs[5] 0 bit 4 r/w rpdrrqs[4] 0 bit 3 r/w rpdrrqs[3] 0 bit 2 r/w rpdrrqs[2] 0 bit 1 r/w rpdrrqs[1] 0 bit 0 r/w rpdrrqs[0] 0 this register provides the packet descriptor reference ready queue start address. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 177 rpdrrqs[15:0]: the receive packet descriptor reference (rpdr) ready queue start bits (rpdrrqs[15:0]) define bits 17 to 2 of the receive packet descriptor reference ready queue start address. this register is initialised by the host. the physical start address of the rpdrr queue is the sum of rpdrrqs[15:0] left shifted by 2 bits with the rqb[31:0] bits in the rmac receive queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 178 register 0x2bc : rmac packet descrip tor reference ready queue write bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdrrqw[15] 0 bit 14 r/w rpdrrqw[14] 0 bit 13 r/w rpdrrqw[13] 0 bit 12 r/w rpdrrqw[12] 0 bit 11 r/w rpdrrqw[11] 0 bit 10 r/w rpdrrqw[10] 0 bit 9 r/w rpdrrqw[9] 0 bit 8 r/w rpdrrqw[8] 0 bit 7 r/w rpdrrqw[7] 0 bit 6 r/w rpdrrqw[6] 0 bit 5 r/w rpdrrqw[5] 0 bit 4 r/w rpdrrqw[4] 0 bit 3 r/w rpdrrqw[3] 0 bit 2 r/w rpdrrqw[2] 0 bit 1 r/w rpdrrqw[1] 0 bit 0 r/w rpdrrqw[0] 0 this register provides the packet descriptor reference ready queue write address. notes 1. this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. 2. if consecutive write accesses to this register are performed, they must be spaced at least 4 sysclk periods apart.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 179 rpdrrqw[15:0]: the receive packet descriptor reference (rpdr) ready queue write bits (rpdrrqw[15:0]) define bits 17 to 2 of the receive packet descriptor reference ready queue write pointer. this register is initialised by the host. the physical write address in the rpdrr queue is the sum of rpdrrqw[15:0] left shifted by 2 bits with the rqb[31:0] bits in the rmac receive queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 180 register 0x2c0 : rmac packet descrip tor reference ready queue read bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdrrqr[15] 0 bit 14 r/w rpdrrqr[14] 0 bit 13 r/w rpdrrqr[13] 0 bit 12 r/w rpdrrqr[12] 0 bit 11 r/w rpdrrqr[11] 0 bit 10 r/w rpdrrqr[10] 0 bit 9 r/w rpdrrqr[9] 0 bit 8 r/w rpdrrqr[8] 0 bit 7 r/w rpdrrqr[7] 0 bit 6 r/w rpdrrqr[6] 0 bit 5 r/w rpdrrqr[5] 0 bit 4 r/w rpdrrqr[4] 0 bit 3 r/w rpdrrqr[3] 0 bit 2 r/w rpdrrqr[2] 0 bit 1 r/w rpdrrqr[1] 0 bit 0 r/w rpdrrqr[0] 0 this register provides the packet descriptor reference ready queue read address. notes 1. this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. 2. if consecutive write accesses to this register are performed, they must be spaced at least 4 sysclk periods apart.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 181 rpdrrqr[15:0]: the receive packet descriptor reference (rpdr) ready queue read bits (rpdrrqr[15:0]) define bits 17 to 2 of the receive packet descriptor reference ready queue read pointer. this register is initialised by the host. the physical read address in the rpdrr queue is the sum of rpdrrqr[15:0] left shifted by 2 bits with the rqb[31:0] bits in the rmac receive queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 182 register 0x2c4 : rmac packet descr iptor reference ready queue end bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w rpdrrqe[15] 0 bit 14 r/w rpdrrqe[14] 0 bit 13 r/w rpdrrqe[13] 0 bit 12 r/w rpdrrqe[12] 0 bit 11 r/w rpdrrqe[11] 0 bit 10 r/w rpdrrqe[10] 0 bit 9 r/w rpdrrqe[9] 0 bit 8 r/w rpdrrqe[8] 0 bit 7 r/w rpdrrqe[7] 0 bit 6 r/w rpdrrqe[6] 0 bit 5 r/w rpdrrqe[5] 0 bit 4 r/w rpdrrqe[4] 0 bit 3 r/w rpdrrqe[3] 0 bit 2 r/w rpdrrqe[2] 0 bit 1 r/w rpdrrqe[1] 0 bit 0 r/w rpdrrqe[0] 0 this register provides the packet descriptor reference ready queue end address. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 183 rpdrrqe[15:0]: the receive packet descriptor reference (rpdr) ready queue end bits (rpdrrqe[15:0]) define bits 17 to 2 of the receive packet descriptor reference ready queue end address. this register is initialised by the host. the physical end address in the rpdrr queue is the sum of rpdrrqe[15:0] left shifted by 2 bits with the rqb[31:0] bits in the rmac receive queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 184 register 0x300 : tmac control bit type func tion default bit 31 to bit 8 unused xxxxxxh bit 7 r/w fqflush 0 bit 6 r/w tdq_frn[1] 0 bit 5 r/w tdq_frn[0] 0 bit 4 r/w tdq_rdyn[2] 0 bit 3 r/w tdq_rdyn[1] 0 bit 2 r/w tdq_rdyn[0] 0 bit 1 r/w cache 1 bit 0 r/w enable 0 this register provides control of the tmac672 block. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. enable: the transmit dma controller enable bit (enable) enables the tmac672 to accept tdrs from the tdr ready queue and reads packet data from host memory. when enable is set high, the tmac672 is enabled. when enable is set low, the tdr ready queue is ignored. once all linked lists of tds built up by the tmac672 have been exhausted, no more data will be transmitted on the td[31:0] links. cache: the transmit descriptor reference cache enable bit (cache) controls the frequency at which tdrs are written to the tdr free queue. when cache is set high, freed tdrs are cached and then written up to six at a time. when cache is set low, freed tdrs are written one at a time.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 185 tdq_rdyn[2:0]: the tdq_rdyn[2:0] field sets the number of transmit descriptor references (tdrs) that must be read from the tdr ready queue before the tdr ready interrupt (tdqrdyi) is asserted, as follows: table 22 ? tdq_rdyn[2:0] settings tdq_rdyn[2:0] no of tdrs 000 1 001 4 010 6 011 8 100 16 101 32 110 reserved 111 reserved tdq_frn[1:0]: the tdq_frn[1:0] field sets the number of times that a block of tdrs are written to the tdr free queue from the tmac672s internal cache before the tdr free queue interrupt (tdqfi) is asserted, as follows: table 23 ? tdq_frn[1:0] settings tdq_frn[1:0] no of reads 00 1 01 4 10 8 11 reserved fqflush: the free queue flush bit (fqflush) may be used to initiate a dump of the free queue cache retained locally within the tmac672 to the free queue located in pci host memory. when the fqflush bit is set high, the tmac672 dumps the contents of the free queue cache to the free queue in pci host memory. the fqflush bit is self clearing and will reset to zero when the flush is complete. setting the fqflush bit to zero has no affect.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 186 register 0x304 : tmac indirect channel provisioning bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r busy x bit 14 r/w rwb 0 bit 13 r/w prov 0 bit 12 to bit 10 unused xh bit 9 r/w chan[9] 0 bit 8 r/w chan[8] 0 bit 7 r/w chan[7] 0 bit 6 r/w chan[6] 0 bit 5 r/w chan[5] 0 bit 4 r/w chan[4] 0 bit 3 r/w chan[3] 0 bit 2 r/w chan[2] 0 bit 1 r/w chan[1] 0 bit 0 r/w chan[0] 0 the channel provisioning register is used to provision and unprovision channels, and also to query the provision status of channels. when a channel is provisioned, chains of packet data for that channel will be accepted by the tmac672 and placed on the channel?s linked list of packets to be transmitted. when a channel is unprov isioned, chains of packet data for that channel will be rejected by the tmac672 and returned to the tdr free queue with the status bits in the queue element set to indicate the rejection. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 187 implemented. however, when all four byte enables are negated, no access is made to this register. chan[9:0]: the indirect data bits (chan[9:0]) report the channel number read from the tmac672 internal memory after an indirect read operation has completed. channel number to be written to the tmac672 internal memory in an indirect write operation must be set up in this register before triggering the write. chan[9:0] reflects the value written until the completion of a subsequent indirect read operation. prov: the indirect provision enable bit (prov) reports the channel provision enable flag read from the tmac672 internal memory after an indirect read operation has completed. the provision enable flag to be written to the tmac672 internal memory, in an indirect write operation, must be set up in this register before triggering the write. when prov is set high, the channel as indicated by chan[9:0] is provisioned. when prov is set low, the channel indicated by chan[9:0] is unprovisioned. prov reflects the value written until the completion of a subsequent indirect read operation. rwb: the read/write bar (rwb) bit selects between a provisioning/unprovisioning operation (write) or a query operation (read). writing a logic 0 to rwb triggers the provisioning or unprovisioning of a channel as specified by chan[9:0] and prov. writing a logic 1 to rwb triggers a query of the channel specified by chan[9:0]. busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operation is available or to determine when a new indirect write operation may commence.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 188 register 0x308 : tmac descriptor table base lsw bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tdtb[15] 0 bit 14 r/w tdtb[14] 0 bit 13 r/w tdtb[13] 0 bit 12 r/w tdtb[12] 0 bit 11 r/w tdtb[11] 0 bit 10 r/w tdtb[10] 0 bit 9 r/w tdtb[9] 0 bit 8 r/w tdtb[8] 0 bit 7 r/w tdtb[7] 0 bit 6 r/w tdtb[6] 0 bit 5 r/w tdtb[5] 0 bit 4 r/w tdtb[4] 0 bit 3 r/w tdtb[3] 0 bit 2 r/w tdtb[2] 0 bit 1 r/w tdtb[1] 0 bit 0 r/w tdtb[0] 0 this register provides the less significant word of the transmit descriptor table base address. the contents of this register is held in a holding register until a write access to the companion tmac transmit descriptor table base msw register. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 189 register 0x30c : tmac descriptor table base msw bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tdtb[31] 0 bit 14 r/w tdtb[30] 0 bit 13 r/w tdtb[29] 0 bit 12 r/w tdtb[28] 0 bit 11 r/w tdtb[27] 0 bit 10 r/w tdtb[26] 0 bit 9 r/w tdtb[25] 0 bit 8 r/w tdtb[24] 0 bit 7 r/w tdtb[23] 0 bit 6 r/w tdtb[22] 0 bit 5 r/w tdtb[21] 0 bit 4 r/w tdtb[20] 0 bit 3 r/w tdtb[19] 0 bit 2 r/w tdtb[18] 0 bit 1 r/w tdtb[17] 0 bit 0 r/w tdtb[16] 0 this register provides the more significant word of the transmit descriptor table base address. the contents of the companion tmac transmit descriptor table base lsw register is held in a holding register until a write access to this register, at which point, the base address of the transmit descriptor table is updated. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 190 tdtb[31:0]: the transmit descriptor table base bits (tdtb[31:0]) provides the base address of the transmit descriptor table in pci host memory. this register is initialised by the host. to calculate the physical address of a td, the 15 bit td offset must be added to bits 31 to 4 of the transmit descriptor table base (tdtb[31:4]). the table must be on a 16 byte boundary and thus the least significant four bits must be written to logic zero.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 191 register 0x310 : tmac queue base lsw bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tqb[15] 0 bit 14 r/w tqb[14] 0 bit 13 r/w tqb[13] 0 bit 12 r/w tqb[12] 0 bit 11 r/w tqb[11] 0 bit 10 r/w tqb[10] 0 bit 9 r/w tqb[9] 0 bit 8 r/w tqb[8] 0 bit 7 r/w tqb[7] 0 bit 6 r/w tqb[6] 0 bit 5 r/w tqb[5] 0 bit 4 r/w tqb[4] 0 bit 3 r/w tqb[3] 0 bit 2 r/w tqb[2] 0 bit 1 r/w tqb[1] 0 bit 0 r/w tqb[0] 0 this register provides the less significant word of the transmit queue base address. the contents of this register is held in a holding register until a write access to the companion tmac transmit queue base msw register. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 192 register 0x314 : tmac queue base msw bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tqb[31] 0 bit 14 r/w tqb[30] 0 bit 13 r/w tqb[29] 0 bit 12 r/w tqb[28] 0 bit 11 r/w tqb[27] 0 bit 10 r/w tqb[26] 0 bit 9 r/w tqb[25] 0 bit 8 r/w tqb[24] 0 bit 7 r/w tqb[23] 0 bit 6 r/w tqb[22] 0 bit 5 r/w tqb[21] 0 bit 4 r/w tqb[20] 0 bit 3 r/w tqb[19] 0 bit 2 r/w tqb[18] 0 bit 1 r/w tqb[17] 0 bit 0 r/w tqb[16] 0 this register provides the more significant word of the transmit queue base address. the contents of the companion tmac transmit descriptor table base lsw register is held in a holding register until a write access to this register, at which point, the base address of the transmit queue is updated. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 193 tqb[31:0]: the transmit queue base bits (tqb[31:0]) provides the base address of the transmit descriptor reference free and transmit descriptor reference ready queue in pci host memory. this register is initialised by the host. to calculate the physical address of a particular transmit queue element, the tqb bits are added with the appropriate queue start, end, read or write index registers to form the physical address. the base address must be dword aligned and thus the least significant two bits must be written to logic zero.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 194 register 0x318 : tmac descripto r reference free queue start bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tdrfqs[15] 0 bit 14 r/w tdrfqs[14] 0 bit 13 r/w tdrfqs[13] 0 bit 12 r/w tdrfqs[12] 0 bit 11 r/w tdrfqs[11] 0 bit 10 r/w tdrfqs[10] 0 bit 9 r/w tdrfqs[9] 0 bit 8 r/w tdrfqs[8] 0 bit 7 r/w tdrfqs[7] 0 bit 6 r/w tdrfqs[6] 0 bit 5 r/w tdrfqs[5] 0 bit 4 r/w tdrfqs[4] 0 bit 3 r/w tdrfqs[3] 0 bit 2 r/w tdrfqs[2] 0 bit 1 r/w tdrfqs[1] 0 bit 0 r/w tdrfqs[0] 0 this register provides the transmit descriptor reference free queue start address. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 195 tdrfqs[15:0]: the transmit packet descriptor reference (tdr) free queue start bits (tdrfqs[15:0]) define bits 17 to 2 of the transmit packet descriptor reference free queue start address. this register is initialised by the host. the physical start address of the tdrf queue is the sum of tdrfqs[15:0] left shifted by 2 bits with the tqb[31:0] bits in the tmac transmit queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 196 register 0x31c tmac descriptor reference free queue write bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tdrfqw[15] 0 bit 14 r/w tdrfqw[14] 0 bit 13 r/w tdrfqw[13] 0 bit 12 r/w tdrfqw[12] 0 bit 11 r/w tdrfqw[11] 0 bit 10 r/w tdrfqw[10] 0 bit 9 r/w tdrfqw[9] 0 bit 8 r/w tdrfqw[8] 0 bit 7 r/w tdrfqw[7] 0 bit 6 r/w tdrfqw[6] 0 bit 5 r/w tdrfqw[5] 0 bit 4 r/w tdrfqw[4] 0 bit 3 r/w tdrfqw[3] 0 bit 2 r/w tdrfqw[2] 0 bit 1 r/w tdrfqw[1] 0 bit 0 r/w tdrfqw[0] 0 this register provides the transmit descriptor reference free queue write address. notes 1. this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. 2. if consecutive write accesses to this register are performed, they must be spaced at least 4 sysclk periods apart.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 197 tdrfqw[15:0]: the transmit packet descriptor reference (tpdr) free queue write bits (tdrfqw[15:0]) define bits 17 to 2 of the transmit packet descriptor reference free queue write pointer. this register is initialised by the host. the physical write address in the tdrf queue is the sum of tdrfqw[15:0] left shifted by 2 bits with the tqb[31:0] bits in the tmac transmit queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 198 register 0x320 : tmac descripto r reference free queue read bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tdrfqr[15] 0 bit 14 r/w tdrfqr[14] 0 bit 13 r/w tdrfqr[13] 0 bit 12 r/w tdrfqr[12] 0 bit 11 r/w tdrfqr[11] 0 bit 10 r/w tdrfqr[10] 0 bit 9 r/w tdrfqr[9] 0 bit 8 r/w tdrfqr[8] 0 bit 7 r/w tdrfqr[7] 0 bit 6 r/w tdrfqr[6] 0 bit 5 r/w tdrfqr[5] 0 bit 4 r/w tdrfqr[4] 0 bit 3 r/w tdrfqr[3] 0 bit 2 r/w tdrfqr[2] 0 bit 1 r/w tdrfqr[1] 0 bit 0 r/w tdrfqr[0] 0 this register provides the transmit descriptor reference free queue read address. notes 1. this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. 2. if consecutive write accesses to this register are performed, they must be spaced at least 4 sysclk periods apart.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 199 tdrfqr[15:0]: the transmit packet descriptor reference (tpdr) free queue read bits (tdrfqr[15:0]) define bits 17 to 2 of the transmit packet descriptor reference free queue read pointer. this register is initialised by the host. the physical read address in the tdrf queue is the sum of tdrfqr[15:0] left shifted by 2 bits with the tqb[31:0] bits in the tmac transmit queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 200 register 0x324 : tmac descriptor reference free queue end bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tdrfqe[15] 0 bit 14 r/w tdrfqe[14] 0 bit 13 r/w tdrfqe[13] 0 bit 12 r/w tdrfqe[12] 0 bit 11 r/w tdrfqe[11] 0 bit 10 r/w tdrfqe[10] 0 bit 9 r/w tdrfqe[9] 0 bit 8 r/w tdrfqe[8] 0 bit 7 r/w tdrfqe[7] 0 bit 6 r/w tdrfqe[6] 0 bit 5 r/w tdrfqe[5] 0 bit 4 r/w tdrfqe[4] 0 bit 3 r/w tdrfqe[3] 0 bit 2 r/w tdrfqe[2] 0 bit 1 r/w tdrfqe[1] 0 bit 0 r/w tdrfqe[0] 0 this register provides the transmit descriptor reference free queue end address. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 201 tdrfqe[15:0]: the transmit packet descriptor reference (tdr) free queue end bits (tdrfqe[15:0]) define bits 17 to 2 of the transmit packet descriptor reference free queue end address. this register is initialised by the host. the physical end address of the tdrf queue is the sum of tdrfqe[15:0] left shifted by 2 bits with the tqb[31:0] bits in the tmac transmit queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 202 register 0x328 :tmac descriptor reference ready queue start bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tdrrqs[15] 0 bit 14 r/w tdrrqs[14] 0 bit 13 r/w tdrrqs[13] 0 bit 12 r/w tdrrqs[12] 0 bit 11 r/w tdrrqs[11] 0 bit 10 r/w tdrrqs[10] 0 bit 9 r/w tdrrqs[9] 0 bit 8 r/w tdrrqs[8] 0 bit 7 r/w tdrrqs[7] 0 bit 6 r/w tdrrqs[6] 0 bit 5 r/w tdrrqs[5] 0 bit 4 r/w tdrrqs[4] 0 bit 3 r/w tdrrqs[3] 0 bit 2 r/w tdrrqs[2] 0 bit 1 r/w tdrrqs[1] 0 bit 0 r/w tdrrqs[0] 0 this register provides the transmit descriptor reference ready queue start address. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 203 tdrrqs[15:0]: the transmit packet descriptor reference (tdr) ready queue start bits (tdrrqs[15:0]) define bits 17 to 2 of the transmit packet descriptor reference ready queue start address. this register is initialised by the host. the physical start address of the tdrf queue is the sum of tdrrqs[15:0] left shifted by 2 bits with the tqb[31:0] bits in the tmac transmit queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 204 register 0x32c : tmac descripto r reference ready queue write bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tdrrqw[15] 0 bit 14 r/w tdrrqw[14] 0 bit 13 r/w tdrrqw[13] 0 bit 12 r/w tdrrqw[12] 0 bit 11 r/w tdrrqw[11] 0 bit 10 r/w tdrrqw[10] 0 bit 9 r/w tdrrqw[9] 0 bit 8 r/w tdrrqw[8] 0 bit 7 r/w tdrrqw[7] 0 bit 6 r/w tdrrqw[6] 0 bit 5 r/w tdrrqw[5] 0 bit 4 r/w tdrrqw[4] 0 bit 3 r/w tdrrqw[3] 0 bit 2 r/w tdrrqw[2] 0 bit 1 r/w tdrrqw[1] 0 bit 0 r/w tdrrqw[0] 0 this register provides the transmit descriptor reference ready queue write address. notes 1. this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. 2. if consecutive write accesses to this register are performed, they must be spaced at least 4 sysclk periods apart.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 205 tdrrqw[15:0]: the transmit packet descriptor reference (tpdr) ready queue write bits (tdrrqw[15:0]) define bits 17 to 2 of the transmit packet descriptor reference ready queue write pointer. this register is initialised by the host. the physical write address in the tdrf queue is the sum of tdrrqw[15:0] left shifted by 2 bits with the tqb[31:0] bits in the tmac transmit queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 206 register 0x330 : tmac descriptor reference ready queue read bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tdrrqr[15] 0 bit 14 r/w tdrrqr[14] 0 bit 13 r/w tdrrqr[13] 0 bit 12 r/w tdrrqr[12] 0 bit 11 r/w tdrrqr[11] 0 bit 10 r/w tdrrqr[10] 0 bit 9 r/w tdrrqr[9] 0 bit 8 r/w tdrrqr[8] 0 bit 7 r/w tdrrqr[7] 0 bit 6 r/w tdrrqr[6] 0 bit 5 r/w tdrrqr[5] 0 bit 4 r/w tdrrqr[4] 0 bit 3 r/w tdrrqr[3] 0 bit 2 r/w tdrrqr[2] 0 bit 1 r/w tdrrqr[1] 0 bit 0 r/w tdrrqr[0] 0 this register provides the transmit descriptor reference ready queue read address. notes 1. this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. 2. if consecutive write accesses to this register are performed, they must be spaced at least 4 sysclk periods apart.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 207 tdrrqr[15:0]: the transmit packet descriptor reference (tpdr) ready queue read bits (tdrrqr[15:0]) define bits 17 to 2 of the transmit packet descriptor reference ready queue read pointer. this register is initialised by the host. the physical read address in the tdrf queue is the sum of tdrrqr[15:0] left shifted by 2 bits with the tqb[31:0] bits in the tmac transmit queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 208 register 0x334 : tmac descriptor reference ready queue end bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w tdrrqe[15] 0 bit 14 r/w tdrrqe[14] 0 bit 13 r/w tdrrqe[13] 0 bit 12 r/w tdrrqe[12] 0 bit 11 r/w tdrrqe[11] 0 bit 10 r/w tdrrqe[10] 0 bit 9 r/w tdrrqe[9] 0 bit 8 r/w tdrrqe[8] 0 bit 7 r/w tdrrqe[7] 0 bit 6 r/w tdrrqe[6] 0 bit 5 r/w tdrrqe[5] 0 bit 4 r/w tdrrqe[4] 0 bit 3 r/w tdrrqe[3] 0 bit 2 r/w tdrrqe[2] 0 bit 1 r/w tdrrqe[1] 0 bit 0 r/w tdrrqe[0] 0 this register provides the transmit descriptor reference ready queue end address. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 209 tdrrqe[15:0]: the transmit packet descriptor reference (tdr) ready queue end bits (tdrrqe[15:0]) define bits 17 to 2 of the transmit packet descriptor reference ready queue end address. this register is initialised by the host. the physical end address of the tdrf queue is the sum of tdrrqe[15:0] left shifted by 2 bits with the tqb[31:0] bits in the tmac transmit queue base register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 210 register 0x380 : thdl indirect channel select bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r busy x bit 14 r/w crwb 0 bit 13 to bit 10 unused xh bit 9 r/w chan[9] 0 bit 8 r/w chan[8] 0 bit 7 r/w chan[7] 0 bit 6 r/w chan[6] 0 bit 5 r/w chan[5] 0 bit 4 r/w chan[4] 0 bit 3 r/w chan[3] 0 bit 2 r/w chan[2] 0 bit 1 r/w chan[1] 0 bit 0 r/w chan[0] 0 this register provides the channel number used to access the transmit channel provision ram. writing to this register triggers an indirect channel register access. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. chan[9:0]: the indirect channel number bits (chan[9:0]) indicate the channel to be configured or interrogated in the indirect access.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 211 crwb: the channel indirect access control bit (crwb) selects between a configure (write) or interrogate (read) access to the channel provision ram. writing a logic zero to crwb triggers an indirect write operation. data to be written is taken from the indirect channel data registers. writing a logic one to crwb triggers an indirect read operation. the data read can be found in the indirect channel data registers. busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operation is available in the thdl indirect channel data #1, #2 and #3 registers or to determine when a new indirect write operation may commence.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 212 register 0x384 : thdl indirect channel data #1 bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w prov 0 bit 14 r/w crc[1] 0 bit 13 r/w crc[0] 0 bit 12 r/w delin 0 bit 11 w reserved x bit 10 w fptr[10] 0 bit 9 w fptr[9] 0 bit 8 w fptr[8] 0 bit 7 w fptr[7] 0 bit 6 w fptr[6] 0 bit 5 w fptr[5] 0 bit 4 w fptr[4] 0 bit 3 w fptr[3] 0 bit 2 w fptr[2] 0 bit 1 w fptr[1] 0 bit 0 w fptr[0] 0 this register contains data read from the channel provision ram after an indirect channel read operation or data to be inserted into the channel provision ram in an indirect channel write operation. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 213 fptr[10:0]: the indirect fifo block pointer (fptr[10:0]) informs the partial packet buffer processor the circular link ed list of blocks to use for a fifo for the channel. the fifo pointer to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. the fifo pointer value can be any one of the block numbers provisioned, by indirect block write operations, to form the circular buffer. reserved: the reserved bit must be set low for correct operation of the freedm- 32p672 device. delin: the indirect delineate enable bit (delin) configures the hdlc processor to perform flag sequence insertion and bit stuffing on the outgoing data stream. the delineate enable bit to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when delin is set high, flag sequence insertion, bit stuffing and ,optionally, crc generation is performed on the outgoing hdlc data stream. when delin is set low, the hdlc processor does not perform any processing (flag sequence insertion, bit stuffing nor crc generation) on the outgoing stream. delin reflects the value written until the completion of a subsequent indirect channel read operation. crc[1:0]: the crc algorithm (crc[1:0]) configures the hdlc processor to perform crc generation on the outgoing hdlc data stream. the value of crc[1:0] to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. crc[1:0] is ignored when delin is low. crc[1:0] reflects the value written until the completion of a subsequent indirect channel read operation. table 24 ? crc[1:0] settings crc[1] crc[0] operation 0 0 no crc 0 1 crc-ccitt 1 0 crc-32 1 1 reserved
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 214 prov: the indirect provision enable bit (prov) reports the channel provision enable flag read from the channel provision ram after an indirect channel read operation has completed. the provision enable flag to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. when prov is set high, the hdlc processor will service requests for data from the tcas672 block. when prov is set low, the hdlc processor will ignore requests from the tcas672 block. prov reflects the value written until the completion of a subsequent indirect channel read operation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 215 register 0x388 : thdl indirect channel data #2 bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w 7bit 0 bit 14 r/w priorityb 0 bit 13 r/w invert 0 bit 12 r/w dfcs 0 bit 11 w reserved 0 bit 10 w flen[10] 0 bit 9 w flen[9] 0 bit 8 w flen[8] 0 bit 7 w flen[7] 0 bit 6 w flen[6] 0 bit 5 w flen[5] 0 bit 4 w flen[4] 0 bit 3 w flen[3] 0 bit 2 w flen[2] 0 bit 1 w flen[1] 0 bit 0 w flen[0] 0 this register contains data to be inserted into the channel provision ram in an indirect write operation. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 216 flen[10:0]: the indirect fifo length (flen[10:0]) is the number of blocks, less one, that is provisioned to the circular channel fifo specified by the fptr[10:0] block pointer. the fifo length to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. reserved: the reserved bit must be set low for correct operation of the freedm- 32p672 device. dfcs: the diagnose frame check sequence bit (dfcs) controls the inversion of the fcs field inserted into the transmit packet. the value of dfcs to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when dfcs is set to one, the fcs field in the outgoing hdlc stream is logically inverted allowing diagnosis of downstream fcs verification logic. the outgoing fcs field is not inverted when dfcs is set to zero. dfcs reflects the value written until the completion of a subsequent indirect channel read operation. invert: the hdlc data inversion bit (invert) configures the hdlc processor to logically invert the outgoing hdlc stream. the value of invert to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when invert is set to one, the outgoing hdlc stream is logically inverted. the outgoing hdlc stream is not inverted when invert is set to zero. invert reflects the value written until the completion of a subsequent indirect channel read operation. priorityb: the active low channel fifo starving enable bit (priorityb) informs the partial packet processor of the priority of the channel relative to other channels when requesting data from the dma port. the value of priorityb to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. channel fifos with priorityb set to one are inhibited from making expedited requests for data to the tmac672. when priorityb is set to zero, both normal and expedited requests can be made to the tmac672. channels with hdlc data rate to fifo size ratio that is significantly lower than other channels should have priorityb set to one. priorityb reflects the value written until the completion of a subsequent indirect channel read operation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 217 7bit: the least significant stuff enable bit (7bit) configures the hdlc processor to stuff the least significant bit of each octet in the corresponding transmit link (td[n]). the value of 7bit to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when 7bit is set high, the least significant bit (last bit of each octet transmitted) does not cont ain channel data and is forced to the value configured by the bit8 register bit. when 7bit is set low, the entire octet contains valid data and bit8 is ignored. 7bit reflects the value written until the completion of a subsequent indirect channel read operation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 218 register 0x38c : thdl indirect channel data #3 bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w trans 0 bit 14 r/w idle 0 bit 13 unused x bit 12 unused x bit 11 r/w level[3] 0 bit 10 r/w level[2] 0 bit 9 r/w level[1] 0 bit 8 r/w level[0] 0 bit 7 r/w flag[2] 0 bit 6 r/w flag[1] 0 bit 5 r/w flag[0] 0 bit 4 unused x bit 3 r/w xfer[3] 0 bit 2 r/w xfer[2] 0 bit 1 r/w xfer[1] 0 bit 0 r/w xfer[0] 0 this register contains data read from the channel provision ram after an indirect read operation or data to be inserted into the channel provision ram in an indirect write operation. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 219 xfer[3:0]: the indirect channel transfer size (xfer[3:0]) specifies the amount of data the partial packet processor requests from the tmac672 block. the channel transfer size to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. when the channel fifo free space reaches or exceeds the limit specified by xfer[3:0], the partial packet processor will make a request for data to the tmac672 to retrieve the xfer[3:0] + 1 blocks of data. fifo free space and transfer size are measur ed in the number of 16-by te blocks. xfer[3:0] reflects the value written until the completion of a subsequent indirect channel read operation. to prevent lockup, the channel transfer size (xfer[3:0]) can be configured to be less than or equal to the start transmission level set by level[3:0] and trans. alternatively, the channel transfer size can be set, such that, the total number of blocks in the logi cal channel fifo minus the start transmission level is an integer multiple of the channel transfer size. the case of a single block transfer size is a special. when bursten is set high and xfer[3:0] = 'b0000, the transfer size is variable. the thdl672 will request the tmac672 to transfer as much data as there is free space in the fifo, up to a maximum set by burst[3:0]. flag[2:0]: the flag insertion control (flag[2:0]) configures the minimum number of flags or bytes of idle bits the hdlc processor inserts between hdlc packets. the value of flag[2:0] to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. the minimum number of flags or bytes of idle (8 bits of 1's) inserted between hdlc packets is shown in the table below. flag[2:0] reflects the value written until the completion of a subsequent indirect channel read operation. table 25 ? flag[2:0] settings flag[2:0] minimum number of flag/idle bytes 000 1 flag / 0 idle byte 001 2 flags / 0 idle byte 010 4 flags / 2 idle bytes 011 8 flags / 6 idle bytes 100 16 flags / 14 idle bytes
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 220 flag[2:0] minimum number of flag/idle bytes 101 32 flags / 30 idle bytes 110 64 flags / 62 idle bytes 111 128 flags / 126 idle bytes level[3:0]: the indirect channel fifo trigger level (level[3:0]), in concert with the trans bit, configure the various channel fifo free space levels which trigger the hdlc processor to start transmission of a hdlc packet as well as trigger the partial packet buffer to make dma request for data as shown in the following table. the channel fifo trigger level to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. level[3:0] reflects the value written until the completion of a subsequent indirect channel read operation. the hdlc processor starts transmitting a packet when the channel fifo free space is less than or equal to the level specified in the appropriate start transmission level column of the following table or when an end of a packet is stored in the channel fifo. when the channel fifo free space is greater than or equal to the level specified in the starving trigger level column of the following table and the hdlc processor is transmitting a packet and an end of a packet is not stored in the channel fifo, the partial packet buffer makes expedite requests to the tmac672 to re trieve xfer[3:0] + 1 blocks of data. to prevent lockup, the channel transfer size (xfer[3:0]) can be configured to be less than or equal to the start transmission level set by level[3:0] and trans. alternatively, the channel transfer size can be set such that the total number of blocks in the logical channel fifo, minus the start transmission level, is an integer multiple of the channel transfer size. the starving trigger level must always be set to a number of blocks greater than or equal to the channel transfer size. idle: the interframe time fill bit (idle) configures the hdlc processor to use flag bytes or hdlc idle as the interframe time fill between hdlc packets. the value of idle to be written to the channel provision ram, in an indirect channel write operation, must be set up in this register before triggering the write. when idle is set low, the hdlc processor uses flag bytes as the interframe time fill. when idle is set high, the hdlc processor uses hdlc idle (all one's bit with no bit-stuffing pattern is transmitted) as the interframe time fill. idle reflects the value written until the completion of a subsequent indirect channel read operation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 221 trans: the indirect transmission start bit (trans), in concert with the level[3:0] bits, configure the various channel fifo free space levels which trigger the hdlc processor to start transmission of a hdlc packet as well as trigger the partial packet buffer to make dma request for data as shown in the following table. the transmission start mode to be written to the channel provision ram, in an indirect write operation, must be set up in this register before triggering the write. trans reflects the value written until the completion of a subsequent indirect channel read operation. the hdlc processor starts transmitting a packet when the channel fifo free space is less than or equal to the level specified in the appropriate start transmission level column of the following table or when an end of a packet is stored in the channel fifo. when the channel fifo free space is greater than or equal to the level specified in the starving trigger level column of the following table and the hdlc processor is transmitting a packet and an end of a packet is not stored in the channel fifo, the partial packet buffer makes expedite requests to the tmac672 to re trieve xfer[3:0] + 1 blocks of data. to prevent lockup, the channel transfer size (xfer[3:0]) can be configured to be less than or equal to the start transmission level set by level[3:0] and trans. alternatively, the channel transfer size can be set, such that, the total number of blocks in the logi cal channel fifo minus the start transmission level is an integer multiple of the channel transfer size. the starving trigger level must always be se t to a number of bl ocks greater than or equal to the channel transfer size. table 26 ? level[3:0]/trans settings level[3:0] starving trigger level start transmission level (trans=0) start transmission level (trans=1) 0000 2 blocks (32 bytes free) 1 block (16 bytes free) 1 block (16 bytes free) 0001 3 blocks (48 bytes free) 2 blocks (32 bytes free) 1 block (16 bytes free) 0010 4 blocks (64 bytes free) 3 blocks (48 bytes free) 2 blocks (32 bytes free) 0011 6 blocks (96 bytes free) 4 blocks (64 bytes free) 3 blocks (48 bytes free) 0100 8 blocks (128 bytes free) 6 blocks (96 bytes free) 4 blocks (64 bytes free)
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 222 level[3:0] starving trigger level start transmission level (trans=0) start transmission level (trans=1) 0101 12 blocks (192 bytes free) 8 blocks (128 bytes free) 6 blocks (96 bytes free) 0110 16 blocks (256 bytes free) 12 blocks (192 bytes free) 8 blocks (128 bytes free) 0111 24 blocks (384 bytes free) 16 blocks (256 bytes free) 12 blocks (192 bytes free) 1000 32 blocks (512 bytes free) 24 blocks (384 bytes free) 16 blocks (256 bytes free) 1001 48 blocks (768 bytes free) 32 blocks (512 bytes free) 24 blocks (384 bytes free) 1010 64 blocks (1 kbytes free) 48 blocks (768 bytes free) 32 blocks (512 bytes free) 1011 96 blocks (1.5 kbytes free) 64 blocks (1 kbytes free) 48 blocks (768 bytes free) 1100 192 blocks (3 kbytes free) 128 blocks (2 kbytes free) 96 blocks (1.5 kbytes free) 1101 384 blocks (6 kbytes free) 256 blocks (4 kbytes free) 192 blocks (2 kbytes free) 1110 768 blocks (12 kbytes free) 512 blocks (8 kbytes free) 384 blocks (4 kbytes free) 1111 1536 blocks (24 kbytes free) 1024 blocks (16 kbytes free) 768 blocks (8 kbytes free)
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 223 register 0x3a0 : thdl indirect block select bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r busy x bit 14 r/w brwb 0 bit 13 to bit 12 unused xh bit 11 r/w reserved x bit 10 r/w block[10] 0 bit 9 r/w block[9] 0 bit 8 r/w block[8] 0 bit 7 r/w block[7] 0 bit 6 r/w block[6] 0 bit 5 r/w block[5] 0 bit 4 r/w block[4] 0 bit 3 r/w block[3] 0 bit 2 r/w block[2] 0 bit 1 r/w block[1] 0 bit 0 r/w block[0] 0 this register provides the block number used to access the block pointer ram. writing to this register triggers an indirect block register access. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 224 block[10:0]: the indirect block number (block[10:0]) indicate the block to be configured or interrogated in the indirect access. reserved: the reserved bit must be set low for correct operation of the freedm- 32p672 device. brwb: the block indirect access control bit (brwb) selects between a configure (write) or interrogate (read) access to the block pointer ram. writing a logic zero to brwb triggers an indirect block write operation. data to be written is taken from the indirect block data register. writing a logic one to brwb triggers an indirect block read operation. the data read can be found in the indirect block data register. busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operation is available in the thdl indirect block data register or to determine when a new indirect write operation may commence.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 225 register 0x3a4 : thdl indirect block data bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w reserved 0 bit 14 to bit 12 unused xh bit 11 r/w reserved x bit 10 r/w bptr[10] 0 bit 9 r/w bptr[9] 0 bit 8 r/w bptr[8] 0 bit 7 r/w bptr[7] 0 bit 6 r/w bptr[6] 0 bit 5 r/w bptr[5] 0 bit 4 r/w bptr[4] 0 bit 3 r/w bptr[3] 0 bit 2 r/w bptr[2] 0 bit 1 r/w bptr[1] 0 bit 0 r/w bptr[0] 0 this register contains data read from the transmit block pointer ram after an indirect block read operation or data to be inserted into the transmit block pointer ram in an indirect block write operation. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 226 bptr[10:0]: the indirect block pointer (bptr[10:0]) configures the block pointer of the block specified by the indirect block select register. the block pointer to be written to the transmit block pointer ram, in an indirect write operation, must be set up in this register before triggering the write. the block pointer value is the block number of the next block in t he linked list. a circular list of blocks must be formed in order to use the block list as a channel fifo buffer. fptr[10:0] reflects the value written until the completion of a subsequent indirect block read operation. when provisioning a channel fifo, all blocks pointers must be re-written to properly initialize the fifo. reserved: the reserved bits must be set low for correct operation of the freedm- 32p672 device.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 227 register 0x3b0 : thdl configuration bit type func tion default bit 31 to bit 10 unused xxxxxxh bit 9 r/w bit8 0 bit 8 r/w tstd 0 bit 7 r/w bursten 0 bit 6 unused x bit 5 unused x bit 4 unused x bit 3 r/w burst[3] 0 bit 2 r/w burst[2] 0 bit 1 r/w burst[1] 0 bit 0 r/w burst[0] 0 this register configures all provisioned channels. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. burst[3:0]: the dma burst length bits (burst[3:0]) configure the maximum amount of transmit data that can be requested in a single dma transaction for channels whose channel transfer size is set to one block (xfer[3:0] = 'b0000). burst[3:0] has no effect when bursten is set low, nor on channels configured with other transfer sizes. burst[3:0] defines the maximum number of 16 byte blocks, less one, that is transferred in each dma transaction. thus, the mi nimum number of blocks is one (16 bytes) and the maximum is sixteen (256 bytes).
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 228 bursten: the burst length enable bit (bursten) controls the use of burst[3:0] in determining the amount of data requested in a single dma transaction for channels whose channel transfer size is set to one block (xfer[3:0] = 'b0000). bursten has no effect on channels configured with other transfer sizes. when bursten is set high, the maximum size of dma transfer is limited by burst[3:0]. the transmit hdlc processor may combine several channel transfer size amounts into a single transaction. when bursten is set low, the amount of data in a dma transfer is limited to one block. tstd: the telecom standard bit (tstd) controls the bit ordering of the hdlc data transferred from the pci host. when tstd is set low, the least significant bit of the each byte on the pci bus (ad[0], ad[8], ad[16] and ad[24]) is the first hdlc bit transmitted and the most significant bit of each byte (ad[7], ad[15], ad[23] and ad[31]) is the last hdlc bit transmitted (datacom standard). when tstd is set high, ad[0], ad[8], ad[16] and ad[24] are the last hdlc bit transmitted and ad[7], ad[15], ad[23] and ad[31] are the first hdlc bit transmitted (telecom standard). bit8: the least significant stuff control bit (bit8) carries the value placed in the least significant bit of each octet when the hdlc processor is configured (7bit set high) to stuff the least significant bit of each octet in the corresponding transmit link (td[n]). when bit8 is set high, the least significant bit (last bit of each octet transmitted) is forced high. when bit8 is set low, the least significant bit is forced low. bit8 is ignored when 7bit is set low.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 229 register 0x400 : tcas indirect link and time-slot select bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r busy x bit 14 r/w rwb 0 bit 13 unused x bit 12 r/w reserved 0 bit 11 r/w reserved 0 bit 10 r/w link[4] 0 bit 9 r/w link[3] 0 bit 8 r/w link[2] 0 bit 7 r/w link[1] 0 bit 6 r/w link[0] 0 bit 5 unused x bit 4 r/w tslot[4] 0 bit 3 r/w tslot[3] 0 bit 2 r/w tslot[2] 0 bit 1 r/w tslot[1] 0 bit 0 r/w tslot[0] 0 this register provides the link number and time-slot number used to access the transmit channel provision ram. writing to this register triggers an indirect register access and transfers the contents of the indirect channel data register to an internal holding register. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 230 tslot[4:0]: the indirect time-slot number bits (tsl ot[4:0]) indicate the time-slot to be configured or interrogated in the indirect access. for a channelised t1/j1 link, time-slots 1 to 24 are valid. for a channelised e1 link, time-slots 1 to 31 are valid. for a h-mvip link, time-slots 0 to 31 are valid. for unchannelised links, only time-slot 0 is valid. link[4:0]: the indirect link number bits (link[4:0]) select amongst the 32 transmit links to be configured or interrogated in the indirect access. reserved: the reserved bits must be set low for correct operation of the freedm- 32p672 device. rwb: the indirect access control bit (rwb) selects between a configure (write) or interrogate (read) access to the transmit channel provision ram. the address to the transmit channel provision ram is constructed by concatenating the tslot[4:0] and link[4:0] bits. writing a logic zero to rwb triggers an indirect write operation. data to be written is taken from the prov and the chan[9:0] bits of the indirect data register. writing a logic one to rwb triggers an indirect read operation. addressing of the ram is the same as in an indirect write operation. the data read can be found in the prov and the chan[9:0] bits of the indirect channel data register. busy: the indirect access status bit (busy) reports the progress of an indirect access. busy is set high when this register is written to trigger an indirect access, and will stay high until the access is complete. at which point, busy will be set low. this register shoul d be polled to determine when data from an indirect read operation is available in the tcas indirect channel data register or to determine when a new indirect write operation may commence.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 231 register 0x404 : tcas indirect channel data bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w prov 0 bit 14 to bit 10 unused xxh bit 9 r/w chan[9] 0 bit 8 r/w chan[8] 0 bit 7 r/w chan[7] 0 bit 6 r/w chan[6] 0 bit 5 r/w chan[5] 0 bit 4 r/w chan[4] 0 bit 3 r/w chan[3] 0 bit 2 r/w chan[2] 0 bit 1 r/w chan[1] 0 bit 0 r/w chan[0] 0 this register contains the data read from the transmit channel provision ram after an indirect read operation or the data to be inserted into the transmit channel provision ram in an indirect write operation. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. chan[9:0]: the indirect data bits (chan[9:0]) report the channel number read from the transmit channel provision ram after an indirect read operation has completed. channel number to be written to the transmit channel provision ram in an indirect write operation must be set up in this register before
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 232 triggering the write. chan[9:0] reflects the value written until the completion of a subsequent indirect read operation. prov: the indirect provision enable bit (prov) reports the channel provision enable flag read from transmit channel provision ram after an indirect read operation has completed. the provision enable flag to be written to the transmit channel provision ram in an indirect write operation must be set up in this register before triggering the write. when prov is set high, the current time-slot is assigned to the channel as indicated by chan[9:0]. when prov is set low, the time-slot does not belong to any channel. the transmit link data is set to the contents of the idle time-slot fill data register. prov reflects the value written until the completion of a subsequent indirect read operation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 233 register 0x408 : tcas framing bit threshold bit type func tion default bit 31 to bit 7 unused xxxxxxxh bit 6 r/w fthres[6] 0 bit 5 r/w fthres[5] 1 bit 4 r/w fthres[4] 0 bit 3 r/w fthres[3] 0 bit 2 r/w fthres[2] 1 bit 1 r/w fthres[1] 0 bit 0 r/w fthres[0] 1 this register contains the threshold used by the clock activity monitors to detect for framing bits/bytes. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. fthres[6:0]: the framing bit threshold bits (fthres[6:0]) contains the threshold used by the clock activity monitor to detect for the presence of framing bits. a counter in the clock activity monitor of each receive link increments on each rising edge of sysclk and is cleared, when the bsync bit of that link is set low, by each rising edge of the corresponding tclk[n]. when the bsync bit of that link is set high, the counter is cleared at every fourth rising edge of the corresponding tclk[n]. when the counter exceeds the threshold given by fthres[6:0], a framing bit/byte has been detected. fthres[6:0] should be set as a function of the sysclk period and the expected gapping width of tclk[n] during data bits and during framing bits/bytes. legal range of fthres[6:0] is 'b0000001 to 'b 1111110.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 234 note: for operation with t1/j1 links and sysclk = 45 mhz, fthresh[6:0] should be set to ?b0100101?. the default value of this register reflects this mode of operation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 235 register 0x40c : tcas idle time-slot fill data bit type func tion default bit 31 to bit 8 unused xxxxxxh bit 7 r/w fdata[7] 1 bit 6 r/w fdata[6] 1 bit 5 r/w fdata[5] 1 bit 4 r/w fdata[4] 1 bit 3 r/w fdata[3] 1 bit 2 r/w fdata[2] 1 bit 1 r/w fdata[1] 1 bit 0 r/w fdata[0] 1 this register contains the data to be written to disabled time-slots of a channelised link. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. fdata[7:0]: the fill data bits (fdata[7:0]) are transmitted during disabled (prov set low) time-slots of channelised links.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 236 register 0x410 : tcas channel disable bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r/w chdis 0 bit 14 to bit 10 unused xxh bit 9 r/w dchan[9] 0 bit 8 r/w dchan[8] 0 bit 7 r/w dchan[7] 0 bit 6 r/w dchan[6] 0 bit 5 r/w dchan[5] 0 bit 4 r/w dchan[4] 0 bit 3 r/w dchan[3] 0 bit 2 r/w dchan[2] 0 bit 1 r/w dchan[1] 0 bit 0 r/w dchan[0] 0 this register controls the disabling of one specific channel to allow orderly provisioning of time-slots. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. dchan[9:0]: the disable channel number bits (dchan[9:0]) selects the channel to be disabled. when chdis is set high, t he channel specified by dchan[9:0] is disabled. data in time-slots associated with the specified channel is set to fdata[7:0] in the idle time-slot fill data register. when chdis is set low, the channel specified by dcha n[9:0] operates normally.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 237 chdis: the channel disable bit (chdis) controls the disabling of the channels specified by dchan[9:0]. when chdis is set high, the channel selected by dchan[9:0] is disabled. data in time-slots associated with the specified channel is set to fdata[7:0] in the id le time-slot fill data register. when chdis is set low, the channel specif ied by dchan[9:0] operates normally.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 238 register 0x480 ? 0x488 : tcas links #0 to #2 configuration bit type func tion default bit 31 to bit 5 unused xxxxxxxh bit 4 r/w bsync 0 bit 3 unused x bit 2 r/w mode[2] 0 bit 1 r/w mode[1] 0 bit 0 r/w mode[0] 0 this register configures operational modes of transmit links #0 to #2. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. mode[2:0]: the mode select bits (mode[2:0]) configures the corresponding transmit link. table 27 details this procedure. when link 4m (0 m 7) is configured for operation in 8.192 mbps h-mvip mode, links 4m+1, 4m+2 and 4m+3 are driven with constant ones. however, links 4m+1, 4m+2 and 4m+3 must be configured for 8.192 mbps h-mvip mode for correct operation of the tcas672. from a channel assignment point of view in the tcas672 (registers 0x100, 0x104), time-slots 0 through 31 of link 4m are mapped to time-slots 0 through 31 of the h-mvip link, time-slots 0 through 31 of link 4m+1 are mapped to time-slots 32 through 63 of the h-mvip link, time-slots 0 through 31 of link 4m+2 are mapped to time-slots 64 through 95 of the h- mvip link and time-slots 0 through 31 of link 4m+3 are mapped to time-slots 96 through 127 of the h-mvip link.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 239 table 27 - transmit links #0 to #2 configuration mode[2:0] link configuration 000 unchannelised 001 channelised t1/j1 (24 time slots labeled 1-24) 010 channelised e1 (31 time slots labeled 1-31) 011 2 mbps h-mvip (32 time slots labeled 0-31) 100 reserved 101 reserved 110 reserved 111 8 mbps h-mvip (128 time slots mapped to time- slots 0 through 31 of links 4m, 4m+1, 4m+2 and 4m+3) bsync: the byte synchronization enable bit (bsync) controls the interpretation of gaps in tclk[n] when link #n is in unchannelised mode (mode[2:0]=?000?). when bsync is set high, the data bit on td[n] clocked in by a downstream device on the first rising edge of tclk[n] after an extended quiescent period is considered to be the most significant bit of a data byte. when bsync is set quiescent, gaps in tclk[n] carry no special significance. bsync is ignored when mode[2:0] ?000?.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 240 register 0x48c ? 0x4fc : tcas links #3 to #31 configuration bit type func tion default bit 31 to bit 3 unused xxxxxxxxh bit 2 r/w mode[2] 0 bit 1 r/w mode[1] 0 bit 0 r/w mode[0] 0 this register configures operational modes of transmit links #3 to #31. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. mode[2:0]: the mode select bits (mode[2:0]) configures the corresponding transmit link. table 28 details this procedure. when link 4m (0 m 7) is configured for operation in 8.192 mbps h-mvip mode, links 4m+1, 4m+2 and 4m+3 are driven with constant ones. however, links 4m+1, 4m+2 and 4m+3 must be configured for 8.192 mbps h-mvip mode for correct operation of the tcas672. from a channel assignment point of view in the tcas672 (registers 0x400, 0x404), time-slots 0 through 31 of link 4m are mapped to time-slots 0 through 31 of the h-mvip link, time-slots 0 through 31 of link 4m+1 are mapped to time-slots 32 through 63 of the h-mvip link, time-slots 0 through 31 of link 4m+2 are mapped to time-slots 64 through 95 of the h- mvip link and time-slots 0 through 31 of link 4m+3 are mapped to time-slots 96 through 127 of the h-mvip link.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 241 table 28 - transmit links #3 to #31 configuration mode[2:0] link configuration 000 unchannelised 001 channelised t1/j1 (24 time slots labeled 1-24) 010 channelised e1 (31 time slots labeled 1-31) 011 2 mbps h-mvip (32 time slots labeled 0-31) 100 reserved 101 reserved 110 reserved 111 8 mbps h-mvip (128 time slots mapped to time- slots 0 through 31 of links 4m, 4m+1, 4m+2 and 4m+3)
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 242 register 0x500 : pmon status bit type func tion default bit 31 to bit 6 unused xxxxxxxh bit 5 r c2det x bit 4 r c1det x bit 3 r ufdet x bit 2 r ofdet x bit 1 unused x bit 0 unused x this register contains status information indicating whether a non-zero count has been latched in the count registers. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register. ofdet: the overflow detect bit (ofdet) indicates the status of the pmon receive fifo overflow count register. ofdet is set high when overflow events have occurred during the latest pmon accumula tion interval. ofdet is set low if no overflow events are detected. ufdet: the underflow detect bit (ufdet) indicates the status of the pmon transmit fifo underflow count register. ufdet is set high when underflow events have occurred during the latest pmon accumulation interval. ufdet is set low if no underflow events are detected. c1det: the configurable event #1 detect bit (c1det) indicates the status of the pmon configurable count #1 register. c1det is set high when selected
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 243 events have occurred during the latest pmon accumulation interval. c1det is set low if no selected events are detected. c2det: the configurable event #2 detect bit (c2det) indicates the status of the pmon configurable count #2 register. c2det is set high when selected events have occurred during the latest pmon accumulation interval. c2det is set low if no selected events are detected.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 244 register 0x504 : pmon receive fifo overflow count bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r of[15] x bit 14 r of[14] x bit 13 r of[13] x bit 12 r of[12] x bit 11 r of[11] x bit 10 r of[10] x bit 9 r of[9] x bit 8 r of[8] x bit 7 r of[7] x bit 6 r of[6] x bit 5 r of[5] x bit 4 r of[4] x bit 3 r of[3] x bit 2 r of[2] x bit 1 r of[1] x bit 0 r of[0] x this register reports the number of receive fifo overflow events in the previous accumulation interval. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 245 of[15:0]: the of[15:0] bits reports the number of receive fifo overflow events that have been detected since the last time this register was polled. this register is polled by writing to the freedm-32p672 master clock / bert activity monitor and accumulation trigger register. the write access transfers the internally accumulated error count to the fifo overflow register and simultaneously resets the internal counter to begin a new cycle of error accumulation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 246 register 0x508 : pmon transm it fifo underflow count bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r uf[15] x bit 14 r uf[14] x bit 13 r uf[13] x bit 12 r uf[12] x bit 11 r uf[11] x bit 10 r uf[10] x bit 9 r uf[9] x bit 8 r uf[8] x bit 7 r uf[7] x bit 6 r uf[6] x bit 5 r uf[5] x bit 4 r uf[4] x bit 3 r uf[3] x bit 2 r uf[2] x bit 1 r uf[1] x bit 0 r uf[0] x this register reports the number of transmit fifo underflow events in the previous accumulation interval. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 247 uf[15:0]: the uf[15:0] bits reports the number of transmit fifo underflow events that have been detected since the last time this register was polled. this register is polled by writing to the freedm-32p672 master clock / bert activity monitor and accumulation trigger register. the write access transfers the internally accumulated error count to the fifo underflow register and simultaneously resets the internal counter to begin a new cycle of error accumulation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 248 register 0x50c : pmon c onfigurable count #1 bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r c1[15] x bit 14 r c1[14] x bit 13 r c1[13] x bit 12 r c1[12] x bit 11 r c1[11] x bit 10 r c1[10] x bit 9 r c1[9] x bit 8 r c1[8] x bit 7 r c1[7] x bit 6 r c1[6] x bit 5 r c1[5] x bit 4 r c1[4] x bit 3 r c1[3] x bit 2 r c1[2] x bit 1 r c1[1] x bit 0 r c1[0] x this register reports the number events, selected by the freedm-32p672 master performance monitor control register, that occurred in the previous accumulation interval. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 249 c1[15:0]: the c1[15:0] bits reports the number of selected events that have been detected since the last time this register was polled. this register is polled by writing to the freedm-32p672 master clock / bert activity monitor and accumulation trigger register. the write access transfers the internally accumulated error count to the configurable count #1 register and simultaneously resets the internal counter to begin a new cycle of event accumulation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 250 register 0x510 : pmon c onfigurable count #2 bit type func tion default bit 31 to bit 16 unused xxxxh bit 15 r c2[15] x bit 14 r c2[14] x bit 13 r c2[13] x bit 12 r c2[12] x bit 11 r c2[11] x bit 10 r c2[10] x bit 9 r c2[9] x bit 8 r c2[8] x bit 7 r c2[7] x bit 6 r c2[6] x bit 5 r c2[5] x bit 4 r c2[4] x bit 3 r c2[3] x bit 2 r c2[2] x bit 1 r c2[1] x bit 0 r c2[0] x this register reports the number events, selected by the freedm-32p672 master performance monitor control register, that occurred in the previous accumulation interval. note this register is not byte addressable. writing to this register modifies all the bits in the register. byte selection using byte enable signals (cbeb[3:0]) are not implemented. however, when all four byte enables are negated, no access is made to this register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 251 c2[15:0]: the c2[15:0] bits reports the number of selected events that have been detected since the last time this register was polled. this register is polled by writing to the freedm-32p672 master clock / bert activity monitor and accumulation trigger register. the write access transfers the internally accumulated error count to the configurable count #2 register and simultaneously resets the internal counter to begin a new cycle of event accumulation.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 252 11 pci configuration register description pci configuration registers are implemented by the pci interface. these registers can only be accessed when the pci interface is a target and a configuration cycle is in progress as indicated using the idsel input. notes on pci configuration register bits: 1. writing values into unused register bits has no effect. however, to ensure software compatibility with future, f eature-enhanced versions of the product, unused register bits must be written with logic zero. reading back unused bits can produce either a logic one or a logic zero; hence unused register bits should be masked off by software when read. 2. except where noted, all configuration bits that can be written into can also be read back. this allows the proc essor controlling the freedm-32p672 to determine the programming state of the block. 3. writable pci configuration register bits are cleared to logic zero upon reset unless otherwise noted. 4. writing into read-only pci configuration register bit locations does not affect freedm-32p672 operation unless otherwise noted. 5. certain register bits are reserved. these bits are associated with megacell functions that are unused in this application. to ensure that the freedm- 32p672 operates as intended, reserved register bits must only be written with their default values. similarly, writing to reserved registers should be avoided. 11.1 pci configuration registers pci configuration registers can only be accessed by the pci host. for each register description below, the hexadecimal register number indicates the pci offset.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 253 register 0x00 : vendor identifi cation/device identification bit type func tion default bit 31 to bit 16 r devid[15:0] 7380h bit 15 to bit 0 r vndrid[15:0] 11f8h vndrid[15:0]: the vndrid[15:0] bits identifies the manu facturer of the device. valid vendor identifiers are allocated by the pci sig. devid[15:0]: the devid[15:0] bits define the particul ar device. valid device identifiers will be specified by pmc-sierra. the default value of devid[15:0] is that of the freedm-32p672 device.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 254 register 0x04 : command/status bit type func tion default bit 31 r/w perr 0 bit 30 r/w serr 0 bit 29 r/w mabt 0 bit 28 r/w rtabt 0 bit 27 r/w tabt 0 bit 26 r dvslt[1] 0 bit 25 r dvslt[0] 1 bit 24 r/w dpr 0 bit 23 r fbtbe 1 bit 22 r reserved 0 bit 21 r 66mhz_capable 1 bit 20 to bit 16 r reserved 00h bit 15 to bit 10 r reserved 00h bit 9 r fbtben 0 bit 8 r/w serren 0 bit 7 r adstp 0 bit 6 r/w perren 0 bit 5 r vgasnp 0 bit 4 r mwai 0 bit 3 r spcen 0 bit 2 r/w mstren 0 bit 1 r/w mcntrl 0 bit 0 r iocntrl 0 the lower 16 bits of this register make up the command register which provides basic control over the gpic's ability to respond to pci accesses. when a 0 is
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 255 written to all bits in the command register, the gpic is logically disconnected from the pci bus for all accesses except configuration accesses. the upper 16- bits is used to record status information for pci bus related events. reads to the status portion of this register behave normally. writes are slightly different in that bits can be reset, but not set. a bit is reset whenever the register is written, and the data in the corresponding bit location is a 1. iocntrl: when iocntrl is set to zero, the gpic will not respond to pci bus i/o accesses. mcntrl: when mcntrl is set to one, the gpic will respond to pci bus memory accesses. clearing mcntrl di sables memory accesses. mstren: when mstren is set to one, the gpic can act as a master. clearing mstren disables the gpic from becoming a master. spcen: the gpic does not decode pci special cycles. the spcen bit is forced low. mwai: the gpic does not generate memory-write-and-invalidate commands. the mwai bit is forced low. vgasnp: the gpic is not a vga device. the vgasnp bit is forced low. perren: when the perren bit is set to one, the gpic can report parity errors. clearing the perren bit causes the gpic to ignore parity errors. adstp: the gpic does not perform address and data stepping. the adstp bit is forced low. serren: when the serren bit is set high, the gpic can drive the serrb line. clearing the serren bit disables the serrb line. serren and perren must be set to report an address parity error.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 256 fbtben: as a master, the gpic does not generate fast back-to-back cycles to different devices. this bit is forced low. the upper 16-bits make up t he pci status field. t he status field tracks the status of pci bus related events. reads to this register behave normally. writes are slightly different in that bits can be reset, but not set. a bit is reset whenever the register is written, and the data in the corresponding bit location is a one. 66mhz_capable: the 66 mhz capable bit is hardwired to one to indicate the gpic is capable of operating in 66 mhz mode. fbtbe: the fbtbe bit is hardwired to one to indicate the gpic supports fast back- to-back transactions with other targets. dpr: the data parity reported (dpr) bit is set high if the gpic is an initiator and asserts or detects a parity error on the perrb signal while the perren bit is set in the command register. the dpr bit is cleared by the pci host. dvslt[1:0]: the device select timing (devslt) bits specify the allowable timings for the assertion of devselb by the gpic as a target. these are encoded as 00b for fast, 01b for medium, 10b for slow and 11b is not used. the gpic allows for medium timing. tabt: the target abort (tabt) bit is set high by the gpic when as a target, it terminates a transaction with a target abort. the tabt bit is cleared by the pci host. rtabt: the received target abort (rtabt) bit is set high by the gpic when as an initiator, its transaction is terminated by a target abort. the rtabt bit is cleared by the pci host. mabt: the master abort (mabt) bit is set high by the gpic when as an initiator, its transaction is terminated by a master abort and a special cycle was not in progress. the mabt bit is cleared by the pci host.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 257 serr: the system error (serr) bit is set high whenever the gpic asserts the serrb output. the serr bit is cleared by the pci host. perr: the parity error (perr) bit is set high whenever the gpic detects a parity error, even if parity error handling is disabled by clearing perren in the command register. the perr bit is cleared by the pci host.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 258 register 0x08 : revision identifier/class code bit type func tion default bit 31 to bit 24 r ccode[23:16] 02h bit 23 to bit 16 r ccode[15:8] 80h bit 15 to bit 8 r ccode[7:0] 00h bit 7 to bit 0 r revid[7:0] 02h revid[7:0]: the revision identifier (revid[7:0]) bits specify a device specific revision identifier and are chosen by pmc-sierra. ccode[23:0]: the class code (ccode[23:0]) bits are divided into three groupings: ccode[23:16] define the base class of the device, ccode[15:8] define the sub-class of the device and ccode[7:0] specify a register specific programming interface. note: base class code: 02h network controller sub-class code: 80h other controllers register class code: 00h none defined.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 259 register 0x0c : cache line size/latency timer/header type bit type func tion default bit 31 to bit 24 r reserved 00h bit 23 r mltfnc 0 bit 22 to bit 16 r hdtype[6:0] 00h bit 15 to bit 8 r/w lt[7:0] 00h bit 7 to bit 0 r/w clsize 00h clsize[7:0]: the cache line size (clsize[7:0]) bits specify the size of the system cacheline in units of dwords. the gpic uses this value to determine the type of read command to issue in a master read transfer. if the transfer size is equal to one, the gpic will issue a me mory read command. if the transfer size is equal to or less than the clsi ze, the gpic will issue a memory read line command. for transfers larger than clsize, the gpic issues a memory read multiple command. lt[7:0]: the latency timer (lt[7:0]) bits specify, in units of the pci clock, the value of the latency timer for the gpic. at reset the value is zero. the value of the lt is application specific and should be programmed by software. hdtype[6:0]: the header type (hdtype[7:0]) bits specify the layout of the base address registers. only the 00h encoding is supported. mltfnc: the multi-function (mltfnc) bit specifies if the gpic supports multiple pci functions. if this bit is set low, the device only supports one function and if the bit is set high, the device supports multi-functions. the mltfnc bit is set low to indicate the gpic only supports one pci function.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 260 register 0x10 : cbi memory base address register bit type func tion default bit 31 to bit 13 r/w bsad[27:9] 00000h bit 12 to bit 4 r bsad[8:0] 000h bit 3 r prftch 0 bit 2 r type[1] 0 bit 1 r type[0] 0 bit 0 r msi 0 the gpic supports memory mapping only. at boot-up the internal registers space is mapped to memory space. the device driver can disable memory space through the pci configuration command register. msi: msi is forced low to indicate that the internal registers map into memory space. type[1:0]: the type field indicates where the internal registers can be mapped. the encoding 00b indicates the registers may be located anywhere in the 32 bit address space, 01b indicates that the registers must be mapped below 1 meg in memory space, 10b indicates the base register is 64 bits and the encoding 11b is reserved. the type field is set to 00b to indicate that the cbi registers can be mapped anywhere in the 32 bit address space. prftch: the prefetchable (prftch) bit is set if there are no side effects on reads and data is returned on all the lanes regardless of the byte enables. otherwise the bit is cleared. tsbs contain registers, such as interrupt status registers, in which bits are cleared on a read. if the pci host is caching data there is a possibility an interrupt status could be lost if data is prefetched, but the cache is flushed and the data is not used. the prftch bit is forced low to indicate that prefetching of data is not supported for internal registers.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 261 bsad[27:0]: the base address (bsad[27:0]) bits defines the size and location of the memory space required for the cbi registers. the bsad[27:0] bits correspond to the most significant 28 bits of the pci address space. the size of the address space required can be determined by writing all ones to base address register and then reading from it. by scanning the returned value from the least significant bit upwards, the size of the required address space can be determined. the binary weighted value of the first one bit found (after the configuration bits) indicates the required amount of space. the bsad[8:0] bits are forced low to indicate that the cbi registers require 8k bytes of memory space. after determining the memory requirements of the cbi registers, the pci host can map them to its desired location by modifying the bsad[27:9] bits in the base address register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 262 register 0x3c : interrupt line / interrupt pin / min_gnt / max_lat bit type func tion default bit 31 to bit 24 r maxlat[7:0] 0fh bit 23 to bit 16 r mingnt[7:0] 05h bit 15 to bit 8 r intpin[7:0] 01h bit 7 to bit 0 r/w intlne[7:0] 00h intlne[7:0]: the interrupt line (intlne[7:0]) field is used to indicate interrupt line routing information. the values in this register are system specific and set by the pci host. intpin[7:0]: the interrupt pin (intpin[7:0]) field is used to specify the interrupt pin the gpic uses. since the gpic will use intab on the pci bus, the value in this register is set to one. mingnt[7:0]: the minimum grant (mingnt[7:0]) field specifies how long of a burst period the bus master needs (in increments of 250 nsec). maxlat[7:0]: the maximum latency (maxlat[7:0]) field specifies how often a bus master needs access to the pci bus (in increments of 250 nsec).
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 263 12 test features description the freedm-32p672 also supports a standard ieee 1149.1 five signal jtag boundary scan test port for use in board testing. all device inputs may be read and all device outputs may be forced via the jtag test port. 12.1 test mode registers test mode registers are used to apply test vectors during production testing of the freedm-32p672. production testing is enabled by asserting the pmctest pin. during production tests, freedm-32p672 registers are selected by the ta[12:0] pins. the address of a register on ta[12:0] is identical to the pci offset of that register when production testing is disabled (pmctest low). read accesses are enabled by asserting trdb low while write accesses are enabled by asserting twrb low. test mode register data is conveyed on the tdat[15:0] pins. test mode registers (as opposed to normal mode registers) are selected when ta[12]/trs is set high.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 264 table 29 ? test mode register memory map address ta[12:0] register 0x0000 - 0x07fc normal mode registers 0x0800 - 0x107c reserved 0x1080 - 0x10fc gpic test registers 0x1100 - 0x11fc rcas test registers 0x1200 - 0x123c rhdl test registers 0x1240 - 0x127c reserved 0x1280 - 0x12fc rmac test registers 0x1300 - 0x137c tmac test registers 0x1380 - 0x13bc thdl test registers 0x13c0 - 0x13fc reserved 0x1400 - 0x14fc tcas test registers 0x1500 - 0x151c pmon test registers 0x1520 - 0x1ffc reserved notes on test mode register bits: 1. writing values into unused register bits has no effect. however, to ensure software compatibility with future, f eature-enhanced versions of the product, unused register bits must be written with logic zero. reading back unused bits can produce either a logic one or a logic zero; hence unused register bits should be masked off by software when read. 2. writable test mode register bits are not initialized upon reset unless otherwise noted. 12.2 jtag test port the freedm-32p672 jtag test access port (tap) allows access to the tap controller and the 4 tap registers: instruction, bypass, device identification and boundary scan. using the tap, device input logic levels can be read, device outputs can be forced, the device can be identified and the device scan path can be bypassed. for more details on the jtag port, please refer to the operations section.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 265 table 30 ? instruction register length - 3 bits instructions selected register instruction code ir[2:0] extest boundary scan 000 idcode identification 001 sample boundary scan 010 bypass bypass 011 bypass bypass 100 stctest boundary scan 101 bypass bypass 110 bypass bypass 111 12.2.1 identification register length - 32 bits version number - 2h part number - 7380h manufacturer's identification code - 0cdh device identification - 273800cdh 12.2.2 boundary scan register the boundary scan register is made up of 365 boundary scan cells, divided into input observation (in_cell), output (out_cell), and bi-directional (io_cell) cells. these cells are detailed in the following pages. the first 32 cells form the id code register, and carry the code 273800cdh. the cells are arranged as follows: table 31 ? boundary scan chain pin/ enable register bit cell type device i.d. rbclk_oen 0 out_cell - rbclk 1 out_cell -
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 266 pin/ enable register bit cell type device i.d. rbd_oen 2 out_cell - rbd 3 out_cell - tmv8dc 4 in_cell - tfp8b 5 in_cell - tmv8fpc 6 in_cell - tfpb[0] 7 in_cell - tmvck[0] 8 in_cell - td_oen[0] 9 out_cell - td[0] 10 out_cell - tclk[0] 11 in_cell - td_oen[1] 12 out_cell - td[1] 13 out_cell - tclk[1] 14 in_cell - td_oen[2] 15 out_cell - td[2] 16 out_cell - tclk[2] 17 in_cell - td_oen[3] 18 out_cell - td[3] 19 out_cell - tclk[3] 20 in_cell - td_oen[4] 21 out_cell - td[4] 22 out_cell - tclk[4] 23 in_cell - td_oen[5] 24 out_cell - td[5] 25 out_cell - tclk[5] 26 in_cell - td_oen[6] 27 out_cell - td[6] 28 out_cell - tclk[6] 29 in_cell - td_oen[7] 30 out_cell -
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 267 pin/ enable register bit cell type device i.d. td[7] 31 out_cell - tclk[7] 32 in_cell - tfpb[1] 33 in_cell - tmvck[1] 34 in_cell - td_oen[8] 35 out_cell - td[8] 36 out_cell - tclk[8] 37 in_cell - td_oen[9] 38 out_cell - td[9] 39 out_cell - tclk[9] 40 in_cell - td_oen[10] 41 out_cell - td[10] 42 out_cell - tclk[10] 43 in_cell - td_oen[11] 44 out_cell - td[11] 45 out_cell - tclk[11] 46 in_cell - td_oen[12] 47 out_cell - td[12] 48 out_cell - tclk[12] 49 in_cell - td_oen[13] 50 out_cell - td[13] 51 out_cell - tclk[13] 52 in_cell - td_oen[14] 53 out_cell - td[14] 54 out_cell - tclk[14] 55 in_cell - td_oen[15] 56 out_cell - td[15] 57 out_cell - tclk[15] 58 in_cell - tfpb[2] 59 in_cell -
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 268 pin/ enable register bit cell type device i.d. tmvck[2] 60 in_cell - td_oen[16] 61 out_cell - td[16] 62 io_cell - tclk[16] 63 in_cell - td_oen[17] 64 out_cell - td[17] 65 io_cell - tclk[17] 66 in_cell - td_oen[18] 67 out_cell - td[18] 68 io_cell - tclk[18] 69 in_cell - td_oen[19] 70 out_cell - td[19] 71 io_cell - tclk[19] 72 in_cell - td_oen[20] 73 out_cell - td[20] 74 io_cell - tclk[20] 75 in_cell - td_oen[21] 76 out_cell - td[21] 77 io_cell - tclk[21] 78 in_cell - td_oen[22] 79 out_cell - td[22] 80 io_cell - tclk[22] 81 in_cell - td_oen[23] 82 out_cell - td[23] 83 io_cell - tclk[23] 84 in_cell - tfpb[3] 85 in_cell - tmvck[3] 86 in_cell - td_oen[24] 87 out_cell - td[24] 88 io_cell -
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 269 pin/ enable register bit cell type device i.d. tclk[24] 89 in_cell - td_oen[25] 90 out_cell - td[25] 91 io_cell - tclk[25] 92 in_cell - td_oen[26] 93 out_cell - td[26] 94 io_cell - tclk[26] 95 in_cell - td_oen[27] 96 out_cell - td[27] 97 io_cell - tclk[27] 98 in_cell - td_oen[28] 99 out_cell - td[28] 100 io_cell - tclk[28] 101 in_cell - td_oen[29] 102 out_cell - td[29] 103 io_cell - tclk[29] 104 in_cell - td_oen[30] 105 out_cell - td[30] 106 io_cell - tclk[30] 107 in_cell - td_oen[31] 108 out_cell - td[31] 109 io_cell - tclk[31] 110 in_cell - tbd 111 in_cell - tbclk_oen 112 out_cell - tbclk 113 out_cell - pmctest 114 in_cell - logic 0 115 in_cell - logic 0 116 in_cell - logic 0 117 in_cell -
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 270 pin/ enable register bit cell type device i.d. m66en 118 in_cell - ad_oen[0] 119 out_cell - ad[0] 120 io_cell - ad_oen[1] 121 out_cell - ad[1] 122 io_cell - ad_oen[2] 123 out_cell - ad[2] 124 io_cell - ad_oen[3] 125 out_cell - ad[3] 126 io_cell - ad_oen[4] 127 out_cell - ad[4] 128 io_cell - ad_oen[5] 129 out_cell - ad[5] 130 io_cell - ad_oen[6] 131 out_cell - ad[6] 132 io_cell - ad_oen[7] 133 out_cell - ad[7] 134 io_cell - cbeb_oen[0] 135 out_cell - cbeb[0] 136 io_cell - ad_oen[8] 137 out_cell - ad[8] 138 io_cell - ad_oen[9] 139 out_cell - ad[9] 140 io_cell - ad_oen[10] 141 out_cell - ad[10] 142 io_cell - ad_oen[11] 143 out_cell - ad[11] 144 io_cell - ad_oen[12] 145 out_cell - ad[12] 146 io_cell -
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 271 pin/ enable register bit cell type device i.d. ad_oen[13] 147 out_cell - ad[13] 148 io_cell - ad_oen[14] 149 out_cell - ad[14] 150 io_cell - ad_oen[15] 151 out_cell - ad[15] 152 io_cell - cbeb_oen[1] 153 out_cell - cbeb[1] 154 io_cell - par_oen 155 out_cell - par 156 io_cell - serrb_oen 157 out_cell - serrb 158 io_cell - perrb_oen 159 out_cell - perrb 160 io_cell - lockb 161 in_cell - stopb_oen 162 out_cell - stopb 163 io_cell - devselb_oen 164 out_cell - devselb 165 io_cell - trdyb_oen 166 out_cell - trdyb 167 io_cell - irdyb_oen 168 out_cell irdyb 169 io_cell - frameb_oen 170 out_cell - frameb 171 io_cell - cbeb_oen[2] 172 out_cell - cbeb[2] 173 io_cell - ad_oen[16] 174 out_cell - ad[16] 175 io_cell -
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 272 pin/ enable register bit cell type device i.d. ad_oen[17] 176 out_cell - ad[17] 177 io_cell - ad_oen[18] 178 out_cell - ad[18] 179 io_cell - ad_oen[19] 180 out_cell - ad[19] 181 io_cell - ad_oen[20] 182 out_cell - ad[20] 183 io_cell - ad_oen[21] 184 out_cell - ad[21] 185 io_cell - ad_oen[22] 186 out_cell - ad[22] 187 io_cell - ad_oen[23] 188 out_cell - ad[23] 189 io_cell - idsel 190 in_cell - cbeb_oen[3] 191 out_cell - cbeb[3] 192 io_cell - ad_oen[24] 193 out_cell - ad[24] 194 io_cell - ad_oen[25] 195 out_cell - ad[25] 196 io_cell - ad_oen[26] 197 out_cell - ad[26] 198 io_cell - ad_oen[27] 199 out_cell - ad[27] 200 io_cell - ad_oen[28] 201 out_cell - ad[28] 202 io_cell - ad_oen[29] 203 out_cell - ad[29] 204 io_cell -
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 273 pin/ enable register bit cell type device i.d. ad_oen[30] 205 out_cell - ad[30] 206 io_cell - ad_oen[31] 207 out_cell - ad[31] 208 io_cell - reqb_oen 209 out_cell - reqb 210 io_cell - logic 0 211 in_cell - gntb 212 in_cell - pciclk 213 in_cell - logic 0 214 in_cell - pciclko_oen 215 out_cell - pciclko 216 out_cell - logic 0 217 in_cell - pciintb_oen 218 out_cell - pciintb 219 io_cell - logic 0 220 in_cell - logic 0 221 in_cell - logic 0 222 in_cell - logic 0 223 in_cell - logic 0 224 in_cell - logic 0 225 in_cell - logic 0 226 in_cell - logic 0 227 in_cell - unconnected 228 out_cell - unconnected 229 io_cell - unconnected 230 out_cell - unconnected 231 io_cell - unconnected 232 out_cell - unconnected 233 io_cell -
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 274 pin/ enable register bit cell type device i.d. unconnected 234 out_cell - unconnected 235 io_cell - unconnected 236 out_cell - unconnected 237 io_cell - unconnected 238 out_cell - unconnected 239 io_cell - unconnected 240 out_cell - unconnected 241 io_cell - unconnected 242 out_cell - unconnected 243 io_cell - unconnected 244 out_cell - unconnected 245 io_cell - unconnected 246 out_cell - unconnected 247 io_cell - unconnected 248 out_cell - unconnected 249 io_cell - unconnected 250 out_cell - unconnected 251 io_cell - unconnected 252 out_cell - unconnected 253 io_cell - unconnected 254 out_cell - unconnected 255 io_cell - unconnected 256 out_cell - unconnected 257 io_cell - unconnected 258 out_cell - unconnected 259 io_cell - unconnected 260 out_cell - unconnected 261 io_cell - unconnected 262 out_cell -
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 275 pin/ enable register bit cell type device i.d. unconnected 263 io_cell - unconnected 264 out_cell - unconnected 265 io_cell - unconnected 266 out_cell - unconnected 267 io_cell - unconnected 268 out_cell - unconnected 269 io_cell - unconnected 270 out_cell - unconnected 271 io_cell - logic 0 272 in_cell - logic 0 273 in_cell - logic 0 274 in_cell - logic 0 275 in_cell - logic 0 276 in_cell - logic 0 277 in_cell - logic 0 278 in_cell - logic 0 279 in_cell - logic 0 280 in_cell - logic 0 281 in_cell - logic 1 282 in_cell - logic 1 283 in_cell - logic 1 284 in_cell - logic 1 285 in_cell - unconnected 286 out_cell - unconnected 287 out_cell - rclk[31] 288 in_cell - rd[31] 289 in_cell - rclk[30] 290 in_cell - rd[30] 291 in_cell -
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 276 pin/ enable register bit cell type device i.d. rclk[29] 292 in_cell - rd[29] 293 in_cell - rclk[28] 294 in_cell - rd[28] 295 in_cell - rclk[27] 296 in_cell - rd[27] 297 in_cell - rclk[26] 298 in_cell - rd[26] 299 in_cell - rclk[25] 300 in_cell - rd[25] 301 in_cell - rclk[24] 302 in_cell - rd[24] 303 in_cell - rmvck[3] 304 in_cell - rfpb[3] 305 in_cell - rclk[23] 306 in_cell - rd[23] 307 in_cell - rclk[22] 308 in_cell - rd[22] 309 in_cell - rclk[21] 310 in_cell - rd[21] 311 in_cell - rclk[20] 312 in_cell - rd[20] 313 in_cell - rclk[19] 314 in_cell - rd[19] 315 in_cell - rclk[18] 316 in_cell - rd[18] 317 in_cell - rclk[17] 318 in_cell - rd[17] 319 in_cell - rclk[16] 320 in_cell -
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 277 pin/ enable register bit cell type device i.d. rd[16] 321 in_cell - rmvck[2] 322 in_cell - rfpb[2] 323 in_cell - rclk[15] 324 in_cell - rd[15] 325 in_cell - rstb 326 in_cell - rclk[14] 327 in_cell - rd[14] 328 in_cell - rclk[13] 329 in_cell - rd[13] 330 in_cell - rclk[12] 331 in_cell - rd[12] 332 in_cell - rclk[11] 333 in_cell 1 rd[11] 334 in_cell 0 rclk[10] 335 in_cell 1 rd[10] 336 in_cell 1 rclk[9] 337 in_cell 0 rd[9] 338 in_cell 0 rclk[8] 339 in_cell 1 rd[8] 340 in_cell 1 rmvck[1] 341 in_cell 0 rfpb[1] 342 in_cell 0 rclk[7] 343 in_cell 0 rd[7] 344 in_cell 0 rclk[6] 345 in_cell 0 rd[6] 346 in_cell 0 sysclk 347 in_cell 0 rclk[5] 348 in_cell 0 rd[5] 349 in_cell 0
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 278 pin/ enable register bit cell type device i.d. rclk[4] 350 in_cell 0 rd[4] 351 in_cell 0 rclk[3] 352 in_cell 1 rd[3] 353 in_cell 1 rclk[2] 354 in_cell 1 rd[2] 355 in_cell 0 rclk[1] 356 in_cell 0 rd[1] 357 in_cell 1 rclk[0] 358 in_cell 1 rd[0] 359 in_cell 1 rmvck[0] 360 in_cell 0 rfpb[0] 361 in_cell 0 rmv8fpc 362 in_cell 1 rfp8b 363 in_cell 0 rmv8dc 364 in_cell 0 tdo tap output - tdi tap input - tck tap clock - tms tap input - trstb tap input - notes: 1. rmv8dc is the first bit of the scan chain (closest to tdi). 2. enable cell pinname_oen, tristates pin pinname when set high. 3. cells ?logic 0? and ?logic 1? are input observation cells whose input pad is bonded to vss or vdd internally. 4. cells titled ?unconnected? are output or bi-directional cells whose pad is unconnected to the device package. in the case of bi-directional cells, the
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 279 pad always drives (i.e. never tri-states) and the pad input is the same logic value as the pad output. figure 17 ? input observation cell (in_cell) input pad d c clock-dr scan chain out input to internal logic shift-dr scan chain in 1 2 mux 1 2 1 2 1 2 i.d. code bit idcode g1 g2 in this diagram and those that follow, clock-dr is equal to tck when the current controller state is shift-dr or capture-dr, and unchanging otherwise. the multiplexor in the center of the diagram selects one of four inputs, depending on the status of select lines g1 and g2. the id code bit is as listed in the table above.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 280 figure 18 ? output cell (out_cell) d c d c g1 g2 12 mux g1 1 1 mux output or enable from system logic scan chain in scan chain out extest output or enable shift-dr clock-dr update-dr 12 12 12 idcode i.d. code bit figure 19 ? bi-directional cell (io_cell) d c d c g1 1 1 mux output from internal logic scan chain in scan chain out extest output to pin shift-dr clock-dr update-dr input from pin input to internal logic g1 1 2 mux 1 2 1 2 1 2 g2 idcode i.d. code bit
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 281 figure 20 ? layout of output en able and bi-directional cells output enable from internal logic (0 = drive) out_cell scan chain out scan chain in input to internal logic output from internal logic i/o pad io_cell scan chain in scan chain out
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 282 13 operations this section presents connection details to the pm4388 toctl device, and operating details for the jtag boundary scan feature. 13.1 toctl connections the required connections between the pm4388 toctl and the freedm- 32p672 are shown in the following table: table 32 ? freedm?toctl connections freedm-32p672 pin direction toctl pin rclk[n] iclk/isig[m] rd[n] id[m] n.c. ifp[m] tclk[n] efp/rclk/esig[m] td[n] ed[m] all 8 framers in the toctl should be programmed to operate in ?clock master: nxds0? mode in both the ingress and egress direction. 13.2 jtag support the freedm-32p672 supports the ieee boundary scan specification as described in the ieee 1149.1 standards. the test access port (tap) consists of the five standard pins, trstb, tck, tms, tdi and tdo used to control the tap controller and the boundary scan registers. the trstb input is the active low reset signal used to reset the tap controller. tck is the test clock used to sample data on input, tdi and to output data on output, tdo. the tms input is used to direct the tap controller through its states. the basic boundary scan architecture is shown below.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 283 figure 21 ? boundary scan architecture boundary scan register control tdi tdo device identification register bypass register instruction register and decode trstb tms tck test access port controller mux dff select tri-state enable the boundary scan architecture consists of a tap controller, an instruction register with instruction decode, a bypass register, a device identification register and a boundary scan register. the tap controller interprets the tms input and generates control signals to load the instruction and data registers. the instruction register with instruction decode block is used to select the test to be executed and/or the register to be accessed. the bypass register offers a single bit delay from primary input, tdi to primary output , tdo. the device identification register contains the device identification code. the boundary scan register allows testing of board inter-connectivity. the boundary scan register consists of a shift register placed in series with device inputs and outputs. using the boundary scan register, all digital inputs can be
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 284 sampled and shifted out on primary output tdo. in addition, patterns can be shifted in on primary input, tdi and forced onto all digital outputs. tap controller the tap controller is a synchronous finite state machine clocked by the rising edge of primary input, tck. all state transitions are controlled using primary input, tms. the finite state machine is described below.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 285 figure 22 ? tap controller finite state machine test-logic-reset run-test-idle select-dr-scan select-ir-scan capture-dr capture-ir shift-dr shift-ir exit1-dr exit1-ir pause-dr pause-ir exit2-dr exit2-ir update-dr update-ir trstb=0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 0 0 0 0 0 1 1 1 1 1 1 all transitions dependent on input tms 0 0 0 0 0 1
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 286 test-logic-reset the test logic reset state is used to disable the tap logic when the device is in normal mode operation. the state is entered asynchronously by asserting input, trstb. the state is entered synchronously regardless of the current tap controller state by forcing input, tms high for 5 tck clock cycles. while in this state, the instruction register is set to the idcode instruction. run-test-idle the run test/idle state is used to execute tests. capture-dr the capture data register state is used to load parallel data into the test data registers selected by the current instruction. if the selected register does not allow parallel loads or no loading is required by the current instruction, the test register maintains its value. loading occurs on the rising edge of tck. shift-dr the shift data register state is used to shift the selected test data registers by one stage. shifting is from msb to lsb and occurs on the rising edge of tck. update-dr the update data register state is used to load a test register's parallel output latch. in general, the output latches are used to control the device. for example, for the extest instruction, the boundary scan test register's parallel output latches are used to control the device's outputs. the parallel output latches are updated on the falling edge of tck. capture-ir the capture instruction register state is used to load the instruction register with a fixed instruction. the load occurs on the rising edge of tck. shift-ir the shift instruction register state is used to shift both the instruction register and the selected test data registers by one stage. shifting is from msb to lsb and occurs on the rising edge of tck.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 287 update-ir the update instruction register state is used to load a new instruction into the instruction register. the new instruction must be scanned in using the shift-ir state. the load occurs on the falling edge of tck. the pause-dr and pause-ir states are provided to allow shifting through the test data and/or instruction registers to be momentarily paused. boundary scan instructions the following is a description of the standard instructions. each instruction selects a serial test data register path between input, tdi and output, tdo. bypass the bypass instruction shifts data from input, tdi to output, tdo with one tck clock period delay. the instruction is used to bypass the device. extest the external test instruction allows testing of the interconnection to other devices. when the current instruction is the extest instruction, the boundary scan register is place between input, tdi and output, tdo. primary device inputs can be sampled by loading the boundary scan register using the capture-dr state. the sampled values can then be viewed by shifting the boundary scan register using the shift-dr state. primary device outputs can be controlled by loading patterns shifted in through input tdi into the boundary scan register using the update-dr state. sample the sample instruction samples all the device inputs and outputs. for this instruction, the boundary scan register is placed between tdi and tdo. primary device inputs and outputs can be sampled by loading the boundary scan register using the capture-dr state. the sampled values can then be viewed by shifting the boundary scan register using the shift-dr state. idcode the identification instruction is used to connect the identification register between tdi and tdo. the device's identification code can then be shifted out using the shift-dr state.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 288 stctest the single transport chain instruction is used to test out the tap controller and the boundary scan register during production test. when this instruction is the current instruction, the boundary scan register is connected between tdi and tdo. during the capture-dr state, the device identification code is loaded into the boundary scan register. the code can then be shifted out output, tdo using the shift-dr state. intest the internal test instruction is used to exercise the device's internal core logic. when this instruction is the current instruction, the boundary scan register is connected between tdi and tdo. during the update-dr state, patterns shifted in on input, tdi are used to drive primary inputs. during the capture-dr state, primary outputs are sampled and loaded into the boundary scan register.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 289 14 functional timing 14.1 receive h-mvip link timing the timing relationship of the receive data clock (rmv8dc), frame pulse clock (rmv8fpc), data (rd[n]) and frame pulse (rfp8b[n]) signals of a link configured for 8.192 mbps h-mvip operation with a type 0 frame pulse is shown in figure 23. the falling edges of each rmv8fpc are aligned to a falling edge of the corresponding rmv8dc for 8.192 mbps h-mvip operation. the freedm-32p672 samples rfp8b low on the falling edge of rmv8fpc and references this point as the start of the next frame. the freedm-32p672 samples the data provided on rd[n] at the ? point of the data bit using the rising edge of rmv8dc as indicated for bit 1 (b1) of time-slot 0 (ts 0) in figure 23. b1 is the most significant bit and b8 is the least significant bit of each octet. time-slots can be ignored by setting the prov bit in the corresponding word of the receive channel provision ram in the rcas672 block to low. figure 23 ? receive 8.192 mbps h-mvip link timing rmv8dc (16 mhz) rfp8b rd[n] b8 b1 b2 b3 b4 b5 b6 b7 b8 b1 ts 127 ts 0 ts 1 rmv8fpc (4 mhz) the timing relationship of the receive data clock (rmvck[n]), data (rd[m], where 8n m 8n+7) and frame pulse (rfpb[n]) signals of a link configured for 2.048 mbps h-mvip operation with a type 0 frame pulse is shown in figure 24. the freedm-32p672 samples rfpb[n] low on the falling edge of the corresponding rmvck[n] and references this point as the start of the next frame. the freedm-32p672 samples the data provided on rd[m] at the ? point of the data bit using the rising edge of the corresponding rmvck[n] as indicated for bit 1 (b1) of time-slot 0 (ts 0) in figure 24. b1 is the most significant bit and b8 is the least significant bit of each octet. time-slots can be ignored by setting the prov bit in the corresponding word of the receive channel provision ram in the rcas672 block to low.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 290 figure 24 ? receive 2.048 mbps h-mvip link timing rfpb[n] rd[m] b8 b1 b2 b3 b4 b5 b6 b7 b8 b1 ts 31 ts 0 ts 1 rmvck[n] (4 mhz) 14.2 transmit h-mvip link timing the timing relationship of the transmit data clock (tmv8dc), frame pulse clock (tmv8fpc), data (td[n]) and frame pulse (tfp8b) signals of a link configured for 8.192 mbps h-mvip operation with a type 0 frame pulse is shown in figure 25. the falling edges of each tmv8fpc are aligned to a falling edge of the corresponding tmv8dc for 8.192 mbps h-mvip operation. the freedm- 32p672 samples tfp8b low on the falling edge of tmv8fpc and references this point as the start of the next frame. the freedm-32p672 updates the data provided on td[n] on every second falling edg e of tmv8dc as indicated for bit 2 (b2) of time-slot 0 (ts 0) in figure 25. the first bit of the next frame is updated on td[n] on the falling tmv8dc clock edge for which tfp8b is also sampled low. b1 is the most significant bit and b8 is the least significant bit of each octet. time-slots that are not provisioned to belong to any channel (prov bit in the corresponding word of the transmit channel provision ram in the tcas672 block set low) transmits the contents of the idle fill time-slot data register. figure 25 ? transmit 8.192 mbps h-mvip link timing tmv8dc (16 mhz) tfp8b td[n] b8 b1 b2 b3 b4 b5 b6 b7 b8 b1 ts 127 ts 0 ts 1 tmv8fpc (4 mhz)
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 291 the timing relationship of the transmit data clock (tmvck[n]), data (td[m], where 8n m 8n+7) and frame pulse (tfpb[n]) signals of a link configured for 2.048 mbps h-mvip operation with a type 0 frame pulse is shown in figure 26. the freedm-32p672 samples tfpb[n] low on the falling edge of the corresponding tmvck[n] and references this point as the start of the next frame. the freedm-32p672 updates the data provided on td[m] on every second falling edge of the corresponding tmvck[n] as indicated for bi t 2 (b2) of time- slot 0 (ts 0) in figure 26. the first bit of the next frame is updated on td[n] on the falling tmvck[n] clock edge for which tfpb[n] is also sampled low. b1 is the most significant bit and b8 is the least significant bit of each octet. time- slots that are not provisioned to belong to any channel (prov bit in the corresponding word of the transmit channel provision ram in the tcas672 block set low) transmits the contents of the idle fill time-slot data register. figure 26 ? transmit 2.048 mbps h-mvip link timing tfpb[n] td[m] b8 b1 b2 b3 b4 b5 b6 b7 b8 b1 ts 31 ts 0 ts 1 tmvck[n] (4 mhz) 14.3 receive non h-mvip link timing the timing relationship of the receive clock (rclk[n]) and data (rd[n]) signals of an unchannelised link is shown in figure 27. the receive data is viewed as a contiguous serial stream. there is no concept of time-slots in an unchannelised link. every eight bits are grouped together into a byte with arbitrary alignment. the first bit received (b1 in figure 27) is deemed the most significant bit of an octet. the last bit received (b8) is deemed the least significant bit. bits that are to be processed by the freedm-32p672 are clocked in on the rising edge of rclk[n]. bits that should be ignored (x in figure 27) are squelched by holding rclk[n] quiescent. in figure 27, the quiescent period is shown to be a low level on rclk[n]. a high level, effected by extending the high phase of the previous valid bit, is also acceptable. selection of bits for processing is arbitrary and is not subject to any byte alignment nor frame boundary considerations.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 292 figure 27 ? unchannelised receive link timing rclk[n] rd[n] b1 b2 b3 b4 x b5 x x x b6 b7 b8 b1 x the timing relationship of the receive clock (rclk[n]) and data (rd[n]) signals of a channelised t1/j1 link is shown in figure 28. the receive data stream is a t1/j1 frame with a single framing bit (f in figure 28) followed by octet bound time-slots 1 to 24. rclk[n] is held quiescent during the framing bit. the rd[n] data bit (b1 of ts1) clocked in by the first rising edge of rclk[n] after the framing bit is the most significant bit of time-slot 1. the rd[n] bit (b8 of ts24) clocked in by the last rising edge of rclk[n] before the framing bit is the least significant bit of time-slot 24. in figure 28, the quiescent period is shown to be a low level on rclk[n]. a high level, effected by extending the high phase of bit b8 of time-slot ts24, is equally acceptable. in channelised t1/j1 mode, rclk[n] can only be gapped during the framing bit. it must be active continuously at 1.544 mhz during all time-slot bits. time-slots can be ignored by setting the prov bit in the corresponding word of the receive channel provision ram in the rcas672 block to low. figure 28 ? channelised t1/j1 receive link timing rclk[n] rd[n] b7b8 f b1b2b3b4b5b6b7b8b1b2b3 ts 24 ts 1 ts 2 the timing relationship of the receive clock (rclk[n]) and data (rd[n]) signals of a channelised e1 link is shown in figure 29. the receive data stream is an e1 frame with a singe framing byte (f1 to f8 in figure 29) followed by octet bound time-slots 1 to 31. rclk[n] is held quiescent during the framing byte. the rd[n] data bit (b1 of ts1) clocked in by the first rising edge of rclk[n] after the framing byte is the most significant bit of time-slot 1. the rd[n] bit (b8 of ts31) clocked in by the last rising edge of rlclk[n] before the framing byte is the least significant bit of time-slot 31. in figure 29, the quiescent period is shown to be a low level on rclk[n]. a high level, effected by extending the high phase of bit b8 of time-slot ts31, is equally acceptable. in channelised e1 mode, rclk[n] can only be gapped during the framing byte. it must be active continuously at 2.048 mhz during all time-slot bits. time-slots can be ignored by setting the
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 293 prov bit in the corresponding word of the receive channel provision ram in the rcas672 block to low. figure 29 ? channelised e1 receive link timing rclk[n] rd[n] b6 b7 f1 f2 f3 f4 f5 f6 f7 f8 b1 b2 b3 ts 31 fas / nfas ts 1 b8 b4 b5 b6 b7 b8 b1 b2 b3 b4 ts 2 14.4 transmit non h-mvip link timing the timing relationship of the transmit clock (tclk[n]) and data (td[n]) signals of a unchannelised link is shown in figure 30. the transmit data is viewed as a contiguous serial stream. there is no concept of time-slots in an unchannelised link. every eight bits are grouped together into a byte with arbitrary byte alignment. octet data is transmitted from most significant bit (b1 in figure 30) and ending with the least significant bit (b8 in figure 30). bits are updated on the falling edge of tclk[n]. a transmit link may be stalled by holding the corresponding tclk[n] quiescent. in figure 30, bits b5 and b2 are shown to be stalled for one cycle while bit b6 is shown to be stalled for three cycles. in figure 30, the quiescent period is shown to be a low level on tclk[n]. a high level, effected by extending the high phase of the previous valid bit, is also acceptable. gapping of tclk[n] can occur arbitrarily without regard to byte nor frame boundaries. figure 30 ? unchannelised transmit link timing tclk[n] td[n] b1 b2 b3 b4 b5 b6 b7 b8 b1 b2 the timing relationship of the transmit clock (tclk[n]) and data (td[n]) signals of a channelised t1/j1 link is shown in figure 31. the transmit data stream is a t1/j1 frame with a single framing bit (f in figure 31) followed by octet bound time-slots 1 to 24. tclk[n] is held quiescent during the framing bit. the most significant bit of each time-slot is transmitted first (b1 in figure 31). the least significant bit of each time-slot is transmitted last (b8 in figure 31). the td[n] bit (b8 of ts24) before the framing bit is the least significant bit of time-slot 24. in figure 31, the quiescent period is shown to be a low level on tclk[n]. a high level, effected by extending the high phase of bit b8 of time-slot ts24, is equally
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 294 acceptable. in channelised t1/j1 mode, tclk[n] can only be gapped during the framing bit. it must be active continuously at 1.544 mhz during all time-slot bits. time-slots that are not provisioned to belong to any channel (prov bit in the corresponding word of the transmit channel provision ram in the tcas672 block set low) transmit the contents of the idle fill time-slot data register. figure 31 ? channelised t1/j1 transmit link timing tclk[n] td[n] b7 b8 b1 b2 b3 b4 b5 b6 b7 b8 b1 b2 b3 ts 24 ts 1 ts 2 f the timing relationship of the transmit clock (tclk[n]) and data (td[n]) signals of a channelised e1 link is shown in figure 32. the transmit data stream is an e1 frame with a singe framing byte (fas/nfas in figure 32) followed by octet bound time-slots 1 to 31. tclk[n] is held quiescent during the framing byte. the most significant bit of each time-slot is transmitted first (b1 in figure 32). the least significant bit of each time-slot is transmitted last (b8 in figure 32). the td[n] bit (b8 of ts31) before the framing byte is the least significant bit of time-slot 31. in figure 32, the quiescent period is shown to be a low level on tclk[n]. a high level, effected by extending the high phase of bit b8 of time-slot 31, is equally acceptable. in channelised e1 mode, tclk[n] can only be gapped during the framing byte. it must be active continuously at 2.048 mhz during all time-slot bits. time-slots that are not provisioned to belong to any channel (prov bit in the corresponding word of the transmit channel provision ram in the tcas672 block set low) transmit the contents of the idle time-slot fill data register. figure 32 ? channelised e1 transmit link timing tclk[n] td[n] b6 b7 b1 b2 b3 ts 31 fas / nfas ts 1 b8 b4 b5 b6 b7 b8 b1 b2 b3 b4 ts 2 14.5 pci interface a pci burst read cycle is shown in figure 33. the cycle is valid for target and initiator accesses. the target is responsible for incrementing the address during
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 295 the data burst. the 't' symbol stands for a turn around cycle. a turn around cycle is required on all signals which can be driven by more than one agent. during clock 1, the initiator drives frameb to indicate the start of a cycle. it also drives the address onto the ad[31:0] bus and drives the c/beb[3:0] lines with the read command. in the example below, the command would indicate a burst read. the irdyb, trdyb and devselb signals are in turnaround mode (i.e. no agent is driving the signals for this clock cycle). this cycle on the pci bus is called the address phase. during clock 2, the initiator ceases to drive the ad[31:0] bus in order that the target can drive it in the next cycle. the initiator also drives the c/beb[3:0] lines with the byte enables for the read data. irdyb is driven active by the initiator to indicate it is ready to accept the data transfer. all subsequent cycles on the pci bus are called data phases. during clock 3, the target claims the transaction by driving devselb active. it also places the first data word onto the ad[31:0] bus and drives trdyb to indicate to the initiator that the data is valid. during clock 4, the initiator latches in the first data word. the target negates trdyb to indicate to the initiator that it is not ready to transfer another data word. during clock 5, the target places the second data word onto the ad[31:0] bus and drives trdyb to indicate to the initiator that the data is valid. during clock 6, the initiator latches the second data word and negates irdyb to indicate to the target that it is not ready for the next transfer. the target shall drive the third data word until the initiator accepts it. during clock 7, the initiator asserts irdyb to indicate to the target it is ready for the third data word. it also negates frameb since this shall be the last transfer. during clock 8, the initiator latches in the last word and negates irdyb. the target, having seen frameb negated in the last clock cycle, negates trdyb and devselb. all of the above signals shall be driven to their inactive state in this clock cycle, except for frameb which shall be tristated. the target shall stop driving the ad[31:0] bus and the initiator shall stop driving the c/beb[3:0] bus; this shall be the turnaround cycle for these signals.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 296 figure 33 ? pci read cycle pciclk frameb ad[31:0] c/beb[3:0] 123456789 irdyb trdyb devselb t address data 1 data 2 data 3 byte enable byte enable byte enable bus cmd t t t t t t a pci burst write transaction is shown in figure 34. the cycle is valid for target and initiator accesses. the target is responsible for incrementing the address for the duration of the data burst. the 't' symbol stands for a turn around cycle. a turn around cycle is required on all signals which can be driven by more than one agent. during clock 1, the initiator drives frameb to indicate the start of a cycle. it also drives the address onto the ad[31:0] bus and drives the c/beb[3:0] lines with the write command (in the above example the command would indicate a burst write). the irdyb, trdyb and devselb signals are in turnaround mode (no agent is driving the signals for this clock cycle). this cycle on the pci bus is called the address phase. during clock 2, the initiator ceases to drive the address onto the ad[31:0] bus and starts driving the first data word. the initiator also drives the c/beb[3:0] lines with the byte enables for the write data. irdyb is driven active by the initiator to indicate it is ready to accept the data transfer. the target claims the transaction by driving devselb active and drives trdyb to indicate to the initiator that it is ready to accept the data. all subsequent cycles on the pci bus are called data phases. during clock 3, the target latches in the first data word. the initiator starts to drive the next data word onto the ad[31:0] lines. during clock 4, the target latches in the second data word. both the initiator and the target indicate that they are not ready to transfer any more data by negating the ready lines.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 297 during clock 5, the initiator is ready to transfer the next data word so it drives the ad[31:0] lines with the third data word and asserts irdyb. the initiator negates frameb since this is the la st data phase of this cycle. the target is still not ready so a wait state shall be added. during clock 6, the target is still not ready so another wait state is added. during clock 7, the target asserts trdyb to indicate that it is ready to complete the transfer. during clock 8, the target latches in the last word and negates trdyb and devselb, having seen frameb negated previously. the initiator negates irdyb. all of the above signals shall be driven to their inactive state in this clock cycle except for frameb which shall be tristated. figure 34 ? pci write cycle pciclk frameb ad[31:0] c/beb[3:0] 12345678 9 irdyb trdyb devselb t address data 1 data 2 data 3 byte en byte en byte enable bus cmd t t t t t the pci target disconnect (figure 35) illust rates the case when the target wants to prematurely terminate the current cycle. note, when the freedm-32p672 is the target, it never prematurely terminates the current cycle. a target can terminate the current cycle by asserting the stopb signal to the initiator. whether data is transferred or not depends on the state of the ready signals at the time that the target disconnects. if the freedm-32p672 is the initiator and the target terminates t he current access, the freedm-32p672 will retry the access after two pci bus cycles. during clock 1, an access is in progress.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 298 during clock 2, the target indicates that it wishes to disconnect by asserting stopb. data may be transferred depending on the state of the ready lines. during clock 3, the initiator negates frameb to signal the end of the cycle. during clock 4, the target negates stopb and devselb in response to the frameb signal being negated. figure 35 ? pci target disconnect pciclk frameb 123 456 t stopb devselb the pci target abort diagram (figure 36) illustrates the case when the target wants to abort the current cycle. note, when the freedm-32p672 is the target, it never aborts the current cycle. a target abort is an indication of a serious error and no data is transferred. a target can terminate the current cycle by asserting stopb and negating devselb. if the freedm-32p672 is the initiator and the target aborts the current access, the abort condition is reported to the pci host. during clock 1, a cycle is in progress. during clock 2, the target negates devselb and trdyb and asserts stopb to indicate an abort condition to the initiator. during clock 3, the initiator negates frameb in response to the abort request. during clock 4, the target negates stopb signal in response to the frameb signal being negated.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 299 figure 36 ? pci target abort pciclk frameb 123 456 t trdyb devselb stopb the pci bus request cycle diagram (fig ure 37) illustrates the case when the initiator is requesting the bus from the bus arbiter. when the freedm-32p672 is the initiator, it requests the pci bus by asserting its reqb output to the central arbiter. the arbiter grants the bus to the freedm-32p672 by asserting the gntb line. the freedm-32p672 will wait till both the frameb and irdyb lines are id le before starting its access on the pci bus. the arbiter can remove the gntb signal at any time, but the freedm-32p672 will complete the current transfer before relinquishing the bus. figure 37 ? pci bus request cycle pciclk reqb 123456 t gntb frameb the pci initiator abort termination diag ram (figure 38) illustrates the case when the initiator aborts a transaction on the pci bus. an initiator may terminate a cycle if no target claims it within five clock cycles. a target may not have responded because it was incapable of dealing with the request or a bad address was generated by the initiator. irdyb must be valid one clock after frameb is deasserted as in a normal cycle. when the
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 300 freedm-32p672 is the initiator and aborts the transaction, it reports the error condition to the pci host. figure 38 ? pci initiator abort termination pciclk frameb 123 456 t trdyb devselb irdyb 7 t t t the pci exclusive lock cycle diagram (f igure 39) illustrates the case when the current initiator locks the pci bus. the freedm-32p672 will never initiate an lock, but will behave appropriately when acting as a target. during clock 1, the present initiator has gained access of the lockb signal and the pci bus. the first cycle of a locked access must be a read cycle. the initiator asserts frameb and drives the address of the target on the ad[31:0] lines. during clock 2, the present initiator asserts lockb to indicate to the target that a locked cycle is in progress. during clock 3, the target samples the asserted lockb signal and marks itself locked. the data cycle has to complete in order for the lock to be maintained. if for some reason the cycle was aborted, the initiator must negate lockb. during clock 4, the data transfer completes and the target is locked. during clock 6, another initiator may use the pci bus but it cannot use the lockb signal. if the other initiator attempts to access the locked target that it did not lock, the target would reject the access. during clock 7, the same initiator that locked this target accesses the target. the initiator asserts frameb and negates lockb to re-establish the lock. during clock 8, the target samp les lockb deasserted and locks itself.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 301 during clock 9, the initiator does not want to continue the lock so it negates lockb. the target samples lockb and frameb deasserted it removes its lock. figure 39 ? pci exclusive lock cycle pciclk frameb ad[31:0] 123 45 678 9 trdyb devselb t address data t irdyb t t t lockb t t t address data t t t fast back-to-back transactions are used by an initiator to conduct two consecutive transactions on the pci bus without the required idle cycle between them. this can only occur if there is a guarantee that there will be no contention between the initiator or targets involved in the two transactions. in the first case, an initiator may perform fast back-to-back transactions if the first transaction is a write and the second transaction is to the same target. all targets must be able to decode the above transaction. in the second case, all of the targets on the pci bus support fast back-to-back transactions, as indicated in the pci status configuration register. the freedm-32p672 only supports the first type of fast back-to-back transactions and is shown in figure 40. during clock 1, the initiator drives frameb to indicate the start of a cycle. it also drives the address onto the ad[31:0] bus and drives the c/beb[3:0] lines with the write command. in this example the command would indicate a single write. the irdyb, trdyb and devselb signals are in turnaround mode and are not being driven for this clock cycle. this cycle on the pci bus is called the address phase. during clock 2, the initiator ceases to drive the address onto the ad[31:0] bus and starts driving the data element. the initiator also drives the c/beb[3:0] lines with the byte enables for the write data. irdyb is driven active by the initiator to indicate that the data is valid.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 302 the initiator negates frameb since this the last data phase of this cycle. the target claims the transaction by driving devselb active and drives trdyb to indicate to the initiator that it is ready to accept the data. during clock 3, the target latches in the data element and negates trdyb and devselb, having seen frameb negated previously. the initiator negates irdyb and drives frameb to start the next cycle. it also drives the address onto the ad[31:0] bus and drives the c/beb[3:0] lines with the write command. in this example the command would indicate a burst write. during clock 4, the initiator ceases to drive the address onto the ad[31:0] bus and starts driving the first data element. the initiator also drives the c/beb[3:0] lines with the byte enables for the write data. irdyb is driven active by the initiator to indicate that the data is valid. the target claims the transaction by driving devselb active and drives trdyb to indicate to the initiator that it is ready to accept the data. during clock 5, the initiator is ready to transfer the next data element so it drives the ad[31:0] lines with the second data element. the initiator negates frameb since this is the last data phase of this cycle. the target accepts the first data element and negates trdyb to indicate its is not ready for the next data element. during clock 6, the target is still not ready so a wait state shall be added. during clock 7, the target asserts trdyb to indicate that it is ready to complete the transfer. during clock 8, the target latches in the last element and negates trdyb and devselb, having seen frameb negated previously. the initiator negates irdyb. all of the above signals shall be driven to their inactive state in this clock cycle, except for frameb which shall be tristated. the target stops driving the ad[31:0] bus and the initiator stops driving the c/beb[3:0] bus. this shall be the turnaround cycle for these signals.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 303 figure 40 ? pci fast back to back pciclk frameb ad[31:0] c/beb[3:0] 123 456789 irdyb trdyb devselb t address data data byte en byte enable bus cmd t t t t t address data bus cmd 14.6 bert interface the timing relationship between the receive link clock and data (rclk[n] / rd[n]) and the receive bert port signals (rbclk / rbd) is shown in figure 41. bert is not supported for h-mvip links. for non h-mvip links, the selected rclk[n] is placed on rbclk after an asynchronous delay. the selected receive link data (rd[n]) is sampled on the rising edge of the associated rclk[n] and transferred to rbd on the falling edge of rbclk. figure 41 ? receive bert port timing rclk[n] rd[n] b1 b2 b3 b4 x b5 x x x b6 b7 b8 b1 x rbclk rbd b1 b2 b3 b4 b5 b6 b7 b8 b1 the timing relationship between the transmit link clock and data (tclk[n] / td[n]) and the transmit bert port signals (tbclk / tbd) is shown in figure 42. bert is not supported for h-mvip links. tclk[n] is shown to have an arbitrary gapping. when tclk[n] is quiescent, tbd is ignored (x in figure 42). the selected tclk[n] is buffered and placed on tbclk. the transmit bert data
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 304 (tbd) is sampled on the rising edge of the tbclk and transferred to the selected td[n] on the falling edge of tclk[n]. figure 42 ? transmit bert port timing tclk[n] tbd b1 b2 b3 b4 x b5 x x x b6 b7 b8 b1 x b2 tbclk td[n] b1 b2 b3 b4 b5 b6 b7 b8 b1
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 305 15 absolute maximum ratings maximum rating are the worst case limits that the device can withstand without sustaining permanent damage. they are not indicative of normal operating conditions. table 33 ? freedm-32p672 absolute maximum ratings case temperature under bias -40c to +85c storage temperature -40c to +125c supply voltage (+3.3 volt v dd3.3 ) -0.3v to +4.6v supply voltage (+2.5 volt v dd2.5 ) -0.3v to +3.5v voltage on any non-pci pin -0.3v to +6.0v voltage on any pci pin -0.5v to v dd3.3 + 0.5v static discharge voltage 1000 v latch-up current 100 ma dc input current 20 ma lead temperature +230c absolute maximum junction temperature +150c
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 306 16 d.c. characteristics (t a = -40c to +85c, v dd3.3 = 3.0 v to 3.6 v, v dd2.5 = 2.3 v to 2.7v) table 34 ? freedm-32p672 d.c. characteristics symbol parameter min typ max units conditions v dd3.3 3.3v power supply 3.0 3.3 3.6 volts note 4. v dd2.5 2.5v power supply 2.3 2.5 2.7 volts note 4. v il pci input low voltage (bidirs) -0.5 0.8 volts guaranteed input low voltage for pci bidirs. v il pci input low voltage (inputs) -0.5 0.6 volts guaranteed input low voltage for pci inputs (pciclk, idsel, lockb, gntb, m66en). v ih pci input high voltage 0.5 * v dd3.3 v dd3.3 + 0.5 volts guaranteed input high voltage for pci inputs/bidirs. v ol output or bi- directional low voltage 0.4 volts i ol = -4 ma for all outputs except tbclk, rbclk, rbd, pciclko, where i ol = -8 ma. note 3. v oh output or bi- directional high voltage 2.4 volts i oh = 4 ma for all outputs except tbclk, rbclk, rbd, pciclko, where i oh = 8 ma. note 3. v t+ schmitt triggered input high voltage 2.0 5.5 volts v t- schmitt triggered input low voltage -0.2 0.6 volts i ilpu input low current +10 45 +100 a v il = gnd, notes 1, 3, 4. i ihpu input high current -10 0 +10 a v ih = v dd , notes 1, 3 i il input low current -10 0 +10 a v il = gnd, notes 2, 3 i ih input high current -10 0 +10 a v ih = v dd , notes 2, 3
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 307 symbol parameter min typ max units conditions c in input capacitance 5 pf excludes package. package typically 2 pf. note 4. c out output capacitance 5 pf all pins. excludes package. package typically 2 pf. note 4. c io bi-directional capacitance 5 pf all pins. excludes package. package typically 2 pf. note 4. l pin pin inductance 2 nh all pins. note 4. i ddop operating current. 245 ma v dd2.5 = 2.7v, outputs unloaded. rclk[31:0] = tclk[31:0] = 2.048 mhz. rmvck[3:0], tmvck[3:0], rmv8dc and tmv8dc tied low. note 4. i ddop operating current. 330 ma v dd2.5 = 2.7v, outputs unloaded. rclk[2:0] = tclk[2:0] = 51.84 mhz. rclk[31:3], tclk[31:3], rmvck[3:0], tmvck[3:0], rmv8dc and tmv8dc tied low. note 4. notes on d.c. characteristics: 1. input pin or bi-directional pin with internal pull-up resistor. 2. input pin or bi-directional pin without internal pull-up resistor. 3. negative currents flow into the device (sinking), positive currents flow out of the device (sourcing). 4. typical values are given as a design aid. the product is not tested to the typical values given in the data sheet.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 308 17 freedm-32p672 timing characteristics (t a = -40c to +85c, v dd3.3 = 3.0 v to 3.6 v, v dd2.5 = 2.3 v to 2.7v) table 35 ? freedm-32p672 link input (figure 43 to figure 46) symbol description min max units rclk[31:0] frequency (see note 3) 1.542 1.546 mhz rclk[31:0] frequency (see note 4) 2.046 2.050 mhz rclk[2:0] frequency (see note 5) 51.84 mhz rclk[31:3] frequency (see note 5) 10 mhz rclk[31:0] duty cycle 40 60 % rmvck[3:0] frequency (see note 6) 4.092 4.100 mhz rmvck[3:0] duty cycle 40 60 % rmv8dc frequency (see note 7) 16.368 16.400 mhz rmv8dc duty cycle 40 60 % rmv8fpc frequency (see note 8) 4.092 4.100 mhz rmv8fpc duty cycle 40 60 % tp mvc rmv8dc to rmv8fpc skew -10 10 ns sysclk frequency ? 45 mhz sysclk duty cycle 40 60 % ts rd rd[2:0] set-up time 1 ns th rd rd[2:0] hold time 2 ns ts rd rd[31:3] set-up time 5 ns th rd rd[31:3] hold time 5 ns ts rd_2mvip rd[31:0] set-up time (2.048 mbps h- mvip mode) 5 ns th rd_2mvip rd[31:0] hold time (2.048 mbps h- mvip mode) 5 ns ts rd_8mvip rd[31:0] set-up time (8.192 mbps h- mvip mode) 5 ns
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 309 symbol description min max units th rd_8mvip rd[31:0] hold time (8.192 mbps h- mvip mode) 5 ns ts rfpb rfpb[3:0] set-up time 50 ns th rfpb rfpb[3:0] hold time 50 ns ts rfp8b rfp8b set-up time 50 ns th rfp8b rfp8b hold time 50 ns ts tbd tbd set-up time (see note 9) 15 ns th tbd tbd hold time 0 ns ? the minimum sysclk frequency is one half of pciclk freqency or 25mhz, whichever is the greater. notes on input timing: 1. when a set-up time is specified between an input and a clock, the set-up time is the time in nanoseconds from the 1.4 volt point of the input to the 1.4 volt point of the clock. 2. when a hold time is specified between an input and a clock, the hold time is the time in nanoseconds from the 1.4 volt point of the clock to the 1.4 volt point of the input. 3. applicable only to channelised t1/j1 links and measured between framing bits. 4. applicable only to channelised e1 links and measured between framing bytes. 5. applicable only to unchannelised links of any format and measured between any two rclk rising edges. 6. applicable only to 2.048 mbps h-mvip links and measured between any two rmvck[n] falling edges. 7. applicable only to 8.192 mbps h-mvip links and measured between any two rmv8dc falling edges. 8. applicable only to h-mvip links and measured between any two rmv8fpc falling edges. 9. tbd set-up time is measured with a 20 pf load on tbclk. the set-up time increases by typically 1 ns for each 10 pf of extra load on tbclk.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 310 figure 43 ? receive data & frame pulse timing (2.048 mbps h-mvip mode) rmvck[n] rfpb[n] ts rfpb th rfpb rd[m] ts rd_2mvip th rd_2mvip (m=8n,8n+1...8n+7) figure 44 ? receive data & frame pulse timing (8.192 mbps h-mvip mode) rmv8fpc rfp8b ts rfp8b th rfp8b rd[n] ts rd_8mvip th rd_8mvip rmv8dc tp mvc
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 311 figure 45 ? receive data timing (non h-mvip mode) rclk[n] ts rd th rd rd[n] figure 46 ? bert input timing tbclk ts tbd th tbd tbd table 36 ? freedm-32p672 link output (figure 47 to figure 50) symbol description min max units tclk[31:0] frequency (see note 4) 1.542 1.546 mhz tclk[31:0] frequency (see note 5) 2.046 2.050 mhz tclk[2:0] frequency (see note 6) 51.84 mhz tclk[31:3] frequency (see note 6) 10 mhz tclk[31:0] duty cycle 40 60 % tmvck[3:0] frequency (see note 7) 4.092 4.100 mhz tmvck[3:0] duty cycle 40 60 % tmv8dc frequency (see note 8) 16.368 16.400 mhz tmv8dc duty cycle 40 60 % tmv8fpc frequency (see note 9) 4.092 4.100 mhz
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 312 symbol description min max units tmv8fpc duty cycle 40 60 % tp mvc tmv8dc to tmv8fpc skew -10 10 ns ts tfpb tfpb[3:0] set-up time 50 ns th tfpb tfpb[3:0] hold time 50 ns ts tfp8b tfp8b set-up time 50 ns th tf8pb tfp8b hold time 50 ns t p td tclk[2:0] low to td[2:0] valid 3 12 ns t p td tclk[31:3] low to td[31:3] valid 4 25 ns t p td_2mvip tmvck[3:0] low to td[31:0] valid (2.048 mbps h-mvip mode) 4 25 ns t p td_8mvip tmv8dc low to td[31:0] valid (8.192 mbps h-mvip mode) 4 25 ns t p rbd rbclk low to rbd valid -5 5 ns notes on output timing: 1. output propagation delay time is the time in nanoseconds from the 1.4 volt point of the reference signal to the 1.4 volt point of the output. 2. maximum and minimum output propagation delays are measured with a 50 pf load on all the outputs, except for the td[2:0] outputs, which are measured with a 20pf load, and the pci outputs/bidirs, which are measured with a 10pf load. maximum propagation delay for td[2:0] increases by typically 1 ns for each 10 pf of extra load. 3. output propagation delays of signal outputs that are specified in relation to a reference output are measured with a 50 pf load on both the signal output and the reference output. 4. applicable only to channelised t1/j1 links and measured between framing bits. 5. applicable only to channelised e1 links and measured between framing bytes. 6. applicable only to unchannelised links of any format and measured between any two tclk rising edges.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 313 7. applicable only to 2.048 mbps h-mvip links and measured between any two tmvck[n] falling edges. 8. applicable only to 8.192 mbps h-mvip links and measured between any two tmv8dc falling edges. 9. applicable only to h-mvip links and measured between any two tmv8fpc falling edges. 10. output tristate delay is the time in nanoseconds from the 1.4 volt point of the reference signal to the point where the total current delivered through the output is less than or equal to the leakage current. figure 47 ? transmit data & frame pulse timing (2.048 mbps h-mvip mode) td[m] tp td_2mvip tmvck[n] tfpb[n] ts tfpb th tfpb (m=8n,8n+1...8n+7)
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 314 figure 48 ? transmit data & frame pulse timing (8.192 mbps h-mvip mode) tmv8dc td[n] tp td_8mvip tmv8fpc tfp8b ts tfp8b th tfp8b tp mvc figure 49 ? transmit data timing (non h-mvip mode) tclk[n] tp td td[n]
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 315 figure 50 ? bert output timing rbclk tp rbd rbd table 37 ? pci interface (figure 51) symbol description min max units pciclk frequency (see note 1) 25 66 mhz pciclk duty cycle 40 60 % ts pci all pci input and bi-directional set- up time to pciclk 4 ns th pci all pci input and bi-directional hold time to pciclk 0.5 ns t p pci pciclk to all pci outputs valid 2 8.5 ns t z pci pci output active from pciclk to tristate 14 ns t zn pci all pci outputs tristate from pciclk to active 2 ns notes on pci timing: 1. pciclk cannot change frequency without resetting the freedm-32p672 device. 2. the phrase ?all pci outputs? in the above table excludes pciintb and pciclko.
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 316 figure 51 ? pci interface timing pciclk tp pci pci output th pci pci input ts pci tz pci pci tristate output data valid tzn pci pci tristate output data valid table 38 ? jtag port interface (figure 52) symbol description min max units tck frequency 1 mhz tck duty cycle 40 60 % ts tms tms set-up time to tck 50 ns th tms tms hold time to tck 50 ns ts tdi tdi set-up time to tck 50 ns th tdi tdi hold time to tck 50 ns t p tdo tck low to tdo valid 2 60 ns
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 317 figure 52 ? jtag port interface timing ts tms th tms tms tck ts tdi th tdi tdi tp tdo tdo tck
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 318 18 ordering and thermal information table 39 ? freedm-32p672 ordering information part no. description PM7380-pi 329 plastic ball grid array (pbga) table 40 ? freedm-32p672 thermal information part no. ambient temperature theta ja PM7380-pi -40c to +85c 25 c/w
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 319 19 mechanical information figure 53 ? 329 pin plastic ball grid array (pbga) note ? the freedm-32p672 is manufactured using the 4-layer variant of the package shown in the drawing below. 0.20 (2x) a e e 1 a1 ball corner d d 1 45 o chamfer 4 places top view b 0.20 (2x) package type : 329 plastic ball grid array - pbga body size : 31 x 31 x 2.33 mm (4 layer) dim. a (2 layer) a 1 a 2 dd 1 ee 1 ij b c (4 layer) d px py aaa bbb min. 2.12 0.50 1.12 30.80 25.50 30.80 25.50 0.60 27.84 27.84 - - nom . 2.33 0.60 1.17 31.00 26.00 31.00 26.00 1.53 1.53 0.76 0.56 1.0 27.94 27.94 - - max. 2.56 0.70 1.22 31.20 26.70 31.20 26.70 0.90 28.04 28.04 0.15 0.15 e - - 1.27 c (2 layer) 0.56 2.12 2.33 2.54 a (4 layer) - - - - -- -- - - a 2 a a 1 seating plane c side view bbb c aaa c c 30 o typ +/- 1 o a1 ball corner bottom view "d" dia. 3 places j i e b a b c d e f g h j k l m n p r t u v w y aa ab ac py px 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 21 23 22 e notes: 1) all dimensions in millimeter. 2) dimension aaa denotes coplanarity. 3) dimension bbb denotes parallel. a1 ball indicator
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 proprietary and confidential to pmc-sierra,inc., and for its customers? internal use 320 notes
released PM7380 freedm-32p672 data sheet pmc-1990262 issue 5 frame engin e and data link manager 32p672 none of the information contained in this document constitutes an express or implied warranty by pmc-sierra, inc. as to the suf ficiency, fitness or suitability for a particular purpose of any such information or the fitness, or suitability for a particular purpose, merc hantab ility, performance, compatibility with other parts or systems, of any of the products of pmc-sierra, inc., or any portion thereof, referred to in this document. pmc-sierra, inc. expressly disclaims all representations and warranties of any kind regarding the contents or use of the information, including, but not l imited to, express and implied warranties of accuracy, completeness, merchantab ility, fitness for a particular use, or non-infringement. in no event will pmc-sierra, inc. be liable for any direct, indirect, special, inci dental or consequential damages, including, but not limited to, lost profits, lost business or lost data resulting from any use of or reliance upon the information, whether or not pmc-sierra, inc. has been advised of the possibility of such damage. the technology discussed is protected by one or more of the following patents: u.s. patent nos. 5,640,398 and 6,188,699 can. patent no. 2,161,921 relevant patent applications and other patents may also exist. ? 2001 pmc-sierra, inc pmc-1990262 (r5) ref pmc-1980531 (r6) issue date: august 2001 pmc-sierra, inc. 8555 baxter place burnaby, bc canada v5a 4v7 604 .415.6000 contacting pmc-sierra, inc. pmc-sierra, inc. 8555 baxter place burnaby, bc canada v5a 4v7 tel: (604) 415-6000 fax: (604) 415-6200 document information: document@pmc-sierra.com corporate information: info@pmc-sierra.com application information: apps@pmc-sierra.com web site: http://www.pmc-sierra.com

▲Up To Search▲

Price & Availability of PM7380

	To Download PM7380 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .